Watson Workspace will no longer be available after February 28, 2019. Learn more.

Ideas

Duplicate spaces

Planned

Comments

11 comments

  • Avatar
    JARED WALLACE

    Thanks for reporting. I've opened up a ticket to track this item.

  • Avatar
    PAUL UNDERHAY

    I was going to post just now on this

    - you can have a space set up called 'ABC'
    - someone else misses that and also sets up a space called 'ABC' (with same participants)

    Would be helpful if the duplication was called out by the tech in the course of setting up the duplicate, i.e.:

    'I've found another space with that name - are you sure you want to set up a new Space called 'ABC'?

  • Avatar
    Ami Dewar

    We've thought about that but when you consider a free offering - do you want to call out every duplicate from anyone?  

  • Avatar
    Sudarshanarao duttaluri

    Hi Ami Dewar,

    Even if it is free, people will be testing it seriously. They will get issues with duplicate names.  Kindly consider it as a production issue and look for a remedy.

    Thank you

    Best regards
    Sudarshan

  • Avatar
    Ami Dewar

    I apologize, I think you are missing my point. Its not about the cost - its about the sheer volume of duplicates that are possible with an offering that anyone in the world can use.  Do you expect that it only recognizes when you, the creator of the space, have a duplicate space, or when there is any space created by anyone that has the same name?

  • Avatar
    PAUL UNDERHAY

    Amy - understand how this might be tough to achieve with the Preview version (although surely the technology could recognise Duplicates within any given user's 'view'?)

    But surely, for Enterprise version, customers should have this capability? Otherwise you are going to have duplicate effort all over the place, something I know we are designing to prevent

  • Avatar
    Ami Dewar

    We aren't planning to limit duplicates.  We want users to be able to quickly create/name a space whatever they want vs. having to find a unique space but we have discussed ideas to accommodate duplicates that an individual user might have and have also talked about "suggested" spaces  - that was also looking at overlapping membership as well as similar "topics".  I could see, in the "convert to space from email" use case, looking for other spaces you might have that are similar/align with the topic/membership of the email and suggesting those spaces vs. creating a new space - but I don't imagine us ever not letting you name a space (ie. Lunch plans) what you want because someone else in the enterprise is/has used that name.  

  • Avatar
    Ami Dewar

    PS.  There really isn't a line - for a user - between free and enterprise.  In other words, as a user I might be part of a paid, enterprise account but belong to spaces that a free user created.  

  • Avatar
    ROBERT INGRAM

    Bit of an aside.  Renaming spaces is something space owners will be able to do very easily if they see a naming problem issue.  Any member can do this today but with enterprise admin controls, that would become something only space owners would do.

  • Avatar
    Daniel Lieber

    Just to provide more context on this issue... within the general public namespace, duplicates should not be generally flagged. It would make sense if an individual member tries to create a space with the same name of which they are already a member, but the names themselves contain metadata that is appropriately likely to be duplicated across clients in a multi-tenant offering. Examples of likely-to-be duplicated spaces could be: Company News, Prospects, Holiday Party Planning.

    For the enterprise level, the ability to rename spaces should be flexible as some enterprises will want it to be the same as the general user population, others will want only owners, and still others will only want company administrators to change the names.

    I hope this helps!

  • Avatar
    Ami Dewar

    Yes, Daniel - that is generally how we are thinking about duplicates. 

Please sign in to leave a comment.