[
http://jira.dspace.org/jira/browse/DS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-510:
---------------------------
Fix Version/s: 1.7
>From discussion of this new feature request during DSpace Developers Meeting
>on 14 April 2010:
[17:04] <tdonohue> Next one: Streamline UI for community/collection role
assignment - http://jira.dspace.org/jira/browse/DS-510
[17:05] <tdonohue> DS-510 is obviously a new feature request....do we like this
idea? thoughts?
[17:05] <stuartlewis> 510: Several requests listed in that issue. Perhaps
better split up?
[17:05] <carynn> in our instance of dspace, i actually assign a "shortname" to
all communities and /or collections, and then use that in a group name...
[17:06] <grahamtriggs> possible feature for next major, but a bit early to say
it will be done
[17:06] <tdonohue> stuartlewis: if you see logical split points feel free to
split up...I was trying to decide if these were interrelated
[17:06] <carynn> grahamtriggs: agreed - there are ways around this for repo
mgrs...
[17:07] <tdonohue> ok..DS-510 we'll leave unassigned and mark as potential for
1.7. May need further splitting up
[17:07] <stuartlewis> They are related, but could possibly be split into
smaller tasks, that was all.
> Streamline UI for community/collection role assignment
> ------------------------------------------------------
>
> Key: DS-510
> URL: http://jira.dspace.org/jira/browse/DS-510
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: JSPUI, XMLUI
> Affects Versions: 1.6.0
> Reporter: Dorothea Salo
> Fix For: 1.7
>
>
> Ideally, DSpace administrators should never need to know or see the database
> name of a group responsible for a given role in a given collection or
> community. The only groups they should interact with by name are groups they
> create, and the special Administrator and Anonymous groups. (Essentially, I
> would like to see the "COLLECTION_{collection's DB ID}_{role name}" names
> disappear completely from the UI.)
> This would require the following UI changes:
> - In the Groups search, return only Administrator, Anonymous, and
> user-created groups.
> - On the Manage Roles page, remove the middle column that contains the
> DSpace-created group names entirely. Move the link to the left-hand column
> containing the name of the action.
> - In the policy authorization page, only permit Administrator, Anonymous, and
> user-created groups in the Groups column. (To make this backward-compatible,
> it may be necessary to come up with verbiage for
> "Submitters/Editors/Collection Administrators on Collection X" and have
> DSpace do the database lookup to fill in the collection name and role.)
> It might even be possible to alter the database to remove the proliferation
> of DSpace-created groups, and doing so might make it easier to "clone" roles
> across collections (very useful!), but I don't have a well-informed opinion
> on how feasible or desirable that is, so I'll leave it to the developers to
> discuss.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
