You are here

Home » API reference » Spaces 7.3

README.txt in Spaces 7.3

Same filename in this branch
  1. 7.3 README.txt
  2. 7.3 spaces_customtext/README.txt
  3. 7.3 spaces_og/README.txt
  4. 7.3 spaces_dashboard/README.txt
  5. 7.3 spaces_taxonomy/README.txt
Same filename and directory in other branches
  1. 7 spaces_taxonomy/README.txt
About Spaces Taxonomy
=====================

A vocabulary is selected that will represent the Space realm and any
node tagged with a term from that Vocabulary will belong to that term
space. A node can only belong to one term space and you can't move it
between term spaces.

It would obviously be a nice to have to support multiple spaces and
moving between spaces but the implementation of both of these is
tricky, in particular questions like:

 1. If you land in node/5 without a PURL modifier which of its multiple
    spaces should spaces push you to? Should it just show it to you out of
    any space context? (often a bad idea)

 2. If you want to move foo/node/5 to bar/node/5, how do you handle any
    associations that may/may not be relevant in the new space? For
    example, imagine moving a casetracker case from a client group to a
    private group -- what should happen to its parent project and any
    email subscriptions for users that aren't in the target space?

These are reasons that term spaces are single selects.

File

spaces_taxonomy/README.txt
View source 
  1. About Spaces Taxonomy

  2. =====================

  3. 

  4. A vocabulary is selected that will represent the Space realm and any

  5. node tagged with a term from that Vocabulary will belong to that term

  6. space. A node can only belong to one term space and you can't move it

  7. between term spaces.

  8. 

  9. It would obviously be a nice to have to support multiple spaces and

  10. moving between spaces but the implementation of both of these is

  11. tricky, in particular questions like:

  12. 

  13.  1. If you land in node/5 without a PURL modifier which of its multiple

  14.     spaces should spaces push you to? Should it just show it to you out of

  15.     any space context? (often a bad idea)

  16. 

  17.  2. If you want to move foo/node/5 to bar/node/5, how do you handle any

  18.     associations that may/may not be relevant in the new space? For

  19.     example, imagine moving a casetracker case from a client group to a

  20.     private group -- what should happen to its parent project and any

  21.     email subscriptions for users that aren't in the target space?

  22. 

  23. These are reasons that term spaces are single selects.