...
NYU will instead focus on Sociable as the primary means of managing the user experience between multiple repositories and Sakai.
The Sociable tool will not store any resource itself, but will instead store and point to a durable URI of the resource, separating the metadata from the storage. Sakai would then use the URI to point to a resource when it is embedded/linked within a content page in Sakai--or a user could choose to point to the Sociable record instead. For example, a user locating a resource using the federated search tool Primo could add this resource to Sociable. Then within Sakai that user could retrieve and embed that resource within a site page using the Sociable tool:
It should be noted that NYU is not making the assumption that K2's JCR will be that store of the metadata and records for searching and tagging. Instead, NYU will conduct an analysis of the various open-source tagging and resource management tools that are available, and select the most appropriate tool to tightly integrate with Sakai. However, Sociable will serve as a system of record for a person's resources, indexing that materials that have been selected by faculty and students for easy retrieval, but avoiding the need for federated search and retrieval mechanisms within Sakai; thereby allowing each repository or applicable search tool to more aptly manage these types of user experiences. NYU will use groups external to Sakai to control access between the systems. See External Groups documentation for more details.
...
In addition, identifying a tool that already does much of the tagging and resource management functionality that users expect has two perceived benefits: 1) the Sakai community doesn't have to spend resources re-creating this functionality; 2) an academic community's resource management needs are insatiable, and another open-source community, in addition to the Sakai community would be vested in the development of new features and functionality within such a tool.