|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
I'm not particularly interested in this feature because we use the collection only to provide type based aggregation for items (article, book, etc.), so really in our case a collection don't need to be shared with other communities (often we only have a single top level community "Research materials", all other views by department, etc. can be provided using discover/browse).
Anyway, I think that the best way to implement this feature is to mimic as much as possible the implementation of the item mapper, so:
1) a new permission for community and collection mapping should be added. By default the community admin (of the owning community) should be able to perform the mapping. The mapping UI tool should work primary at the community level, it will be nice if a move tool will be provided to (like the move feature in edit-item that is able to change the owning collection and change an existent mapping)
2) introduce the concept of "owningCommunity"
3) we already have problem with the current breadcrumb implementation, it doesn't respect the navigation history of the user: are you go to the item page from a browse, a search, from a mapped collection, etc.
for the mapped items
see for example http://demo.dspace.org/jspui/handle/10673/4
we only show the owning collection path in the breadcrumb
4) in this case IMHO it could be better if all the parent paths are shown, as this primary matter for the search box inside the collection home page that could be reached from different communities. Implementing this could be difficult so it could be also delayed to a future improvement.
Finally, we need to pay attention to avoid cyclic graph in community - community - collection relationship
Community ComA
- Community ComB
--- Collection ColA
Community ComC
-(map) Community ComA
The community ComC should be not mappable in ComA or ComB.
Hope this help,
Andrea