Thanks for the comment. I think what you're suggesting is a cool idea. As you suggest, there are challenges related to permissions, which in Clearspace are scoped to the space, not a particular piece of content. For example, imagine that a document was created in a space that I don't have permission to view, but "aliased" to a space that I do. Should I be able to see the document? Simply checking to see if I have permission to view documents in the space wouldn't be enough.
I really like the idea of referencing by name in links.
Thanks for the feedback Steve...after typing this up...I thought up about
it...and I figured that if you are leaving an Alias somewhere....I would
expect (being the requirements provider) to have minimum Anonymous level
access defined in the community where the alias resides, if I do not
already have permissions in that community that give me more
permissions..or have explicit denied permissions conversely. I dont think
that the URLs should change taking you into the community...but more that
the Alias's are document that serve as managed portal into pieces of
content into other communities...likewise, any comments/ratings left on
the Alias should (in my opinion) be left attached to the Alias document.
Perhaps a utility could be provided to the original document owner to view
all Comments in one screen...but I definitely think that an Alias is an
entity like a document..the content just happens to be a pointer.
I prime example of something like this would be a private document that is
in an internal only community, that is Aliased externally into public
communities (such as best practices, rules, agreements, process
definitions)....just some ideas...I'd be happy to brainstorm if you think
this might become an interesting feature. One thing, this could be a
mechanism to help bleed the lines of community barriers when having to
make decisions of Tag Group vs. Community as an informational architecture
Hope this helps...=)
This would be really useful for our community as we try to reduce the number of duplicate documents. We end up having to create a collaboration document with a link to the original (meaning an extra click for the user).
Is there an "idea" for this I can vote up?