Dear developers,
I would like to ask your opinion regarding the issue
<https://jira.duraspace.org/browse/DS-491>
https://jira.duraspace.org/browse/DS-491 for the ability to map collections
to multiple communities.
There are some issues that arose while trying to implement this feature. I
mention them here:
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?
During the last dev meeting on Weds, July 24, 2013, we discussed some of
them (
<https://jira.duraspace.org/browse/DS-491?focusedCommentId=28722&page=com.at
lassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28722>
https://jira.duraspace.org/browse/DS-491?focusedCommentId=28722&page=com.atl
assian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-28722)
Most of us agreed that the collection must have an "owning community" which
is always the community under which the collection was initially created.
Thus, I guess this solves problem number 2 but not 1, 3 and 4. 3 and 4 can
be solved if we display the "owning community" in the breadcrumb (I do not
know if this is correct).
I would like to hear your opinion in order for this issue to be solved and
be included in 4.0.
Regards,
Kostas Stamatis
------------------------------------------------------------------------------
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
