Contribute to the DSpace Development Fund
The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.
| Title (Goal) | Allowing end users to extend, correct or enhance metadata on existing, already archived items |
|---|---|
| Primary Actor | Human |
| Scope | Submission workflow, versioning |
| Level | |
| Story (A paragraph or two describing what happens) | The IR holds a collection of alumni photographs. Sally is an alumnus who was invited to look at the collection, login and tag any of the other alumni she recognizes. Professor Pete is browsing the collection of his department. He notices someone made a spelling error on a subject or another metadata field. This aggrevates him. As a member of the institution and able to login to the system, he expects that he's able to jump in and at least make a suggestion for a correction that is swiftly enforced/implemented. |
Overview
Content Tools
All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license
, unless otherwise noted.
3 Comments
emilio lorenzo
As Bram pointed, this is variation of the use case End User - Item editing by original submitters (see my opinion to that use case) with some very similar implications
But for this particular case, we implemented a "suggest a correction to this item" button on the item-summary-view. An e-mail with the end user comment (only logged-in users to prevent spam) is sent to the general administrator (well, the email, configured in a variable in dspace.cfg) for further action.
If you considered it suitable, i would create a JIRA issue and we will provide the code.
dschuster
I like this idea, but not emailing the administrator, but maybe the Administrators of the Collection and if there isn't one then the general administrator.
With all of the different groups working in DSpace I am the General Administrator, but I would like to push the responsibility out to those "managing" the collection.
I would say YES please create the JIRA and provide the code!!
emilio lorenzo
We liked also that idea of emailing Collection-Administrators (the code was developed for a repository with that permission structure) but the logic was "not so simple" There were items mapped to several collections (uooppps) and things like that...We opted to a simpler aproach.
Anyway, we have created the JIRA and hope to attach the code.(and documented) soon....