[
https://jira.duraspace.org/browse/DS-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28502#comment-28502
]
Kostas Stamatis commented on DS-491:
------------------------------------
While I was digging the code to fix this issue, some concerns were raised
regarding the assignment of a collection to more than one community:
1) Who will be able to do these assignments? Sys admin? Or the community admin
as well? What happens when the community admins (from the communities that will
host the same collection) are different? Should we permit only from an edit
community form to specify the child collections or should we also allow in edit
collection form parent communities to be specified?
2) What happens with the collection policies? If the collection policies are
inherited from the parent community, if this collection belongs to a new
community as well, and the second community has different policies, which
community's policies will be inherited by the collection?
3) Regarding UI, in a collection's home page, the breadcrumb displays the
father community. As long as this collection has one parent community this
works well. What should happen if there are two parent communities?
4) The same problem can be found also in the same page in the search box in the
"select" scope. Which community must appear there?
To check all the aforementioned, please visit http://dspace.kstamatis.gr (admin
credentials: [email protected] / {our_beloved_repository_software_small_case}).
Try to create some collections and communities. When editing a community, two
select boxes allow you to select to add or remove specific collections.
The following apply to this demo:
1) Only sys admin can do that (at least in the UI, because internally,
authorization is checked but I guess that a community admin would also pass
this authorization to add/remove a collection from his community)
2) From a community, you can remove any of the child collections apart from
those that do not appear to any other community (should it be like that? If not
so, you wouldn't be able to see the collection under any of the communities...)
3) In a community, you can add any of the collections of the system, apart from
those that are already childs of this community
4) Only when editing a community can someone specify child collections (Should
we allow when editing a collection to specify its parent communities?)
5) Regarding aforementioned UI issues, the first community is shown
If anyone wants to review the code, please check:
(https://github.com/kstamatis/DSpace/commits/DS-491)
https://github.com/kstamatis/DSpace/commit/0ed43e8bb63da3fb4b1b44b1847d88ca54c9e8f8
Thanks!
> Ability to map collections to multiple communities
> --------------------------------------------------
>
> Key: DS-491
> URL: https://jira.duraspace.org/browse/DS-491
> Project: DSpace
> Issue Type: New Feature
> Reporter: Sarah Shreeves
> Assignee: Kostas Stamatis
> Priority: Major
>
> I searched to see whether this had been requested before but could not see it.
> As a repo manager of an increasingly complex repository (IDEALS), I am
> getting more and more requests to have a collection appear in more than one
> community. For example, we have a joint grant activity between the Library
> School and the Library which has produced a series of reports. Both units
> would like to have these items included in their community under a collection
> specifically for the grant activity. Right now, the only way to do this is to
> create two separate collections, submit items to one collection, and then map
> them to the other collection (which is a tedious process in and of itself
> especially since the search functionality is so problematic there).
> Another example which I'm faced with right now is a collection that will
> include a series of reports that are jointly published by two departments.
> The administrators would like to see this series appear in the community for
> each department, but they would also like to be able to include the handle
> for the entire series on each report (i.e. the collection handle). Right now,
> they either have to choose a 'canonical' collection between the two or we
> have to create a separate community and collection divorced from the
> department communities.
> I would like to see a way where I could map an entire collection so that the
> collection can appear in multiple communities. I would assume that the items
> in that collection would also be mapped. There would be a single handle for
> that collection (essentially the same way the item mapper works).
> This request has come in to me about five or six times now, and it seems that
> the more interdisciplinary work we get into the repository - particularly if
> we're looking at collections of works, not just items - the more necessary
> this kind of functionality will be. It also seems important for a publication
> series where the collection really groups items that belong together.
> I'm happy to answer any questions that you might have about this!
--
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
