A supplemental thought in the usability department.
If I have a bunch of stuff on screen that I want to associate
or otherwise point to in another registry, I can probably
figure out a GUI mechanism to allow me to quickly tag items
and then pull up a view in another registry and hit - associative
link to "this stuff here".
But what is happening under the hood? I think creating the
links is all covered off in RIM today. But if I then think - instead of
link -
export the stuff I just tagged - and then import into the
remote registry underneath that classification - or even,
replicate classification and import as a chunk of content.
It's support for those actions that I'm wanting from the
user point of view since I've found that right now - when
I develop content in my "Test" environment - there is
no clean way to get it over to "Production".
Notice the issues revolve around "preserve UUIDs", as
opposed to create new UUIDs, and the choice of
either update all references to the old UUIDs with
the new equivalent ones instead - so all
the content interactions are replicated across in the target
system.
