MARC tag/field edit permissions
Bug #1297836 reported by
Elaine Hardy
This bug affects 12 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Wishlist item from the Cataloging Interest Group meeting Evergreen 2014.
Within MARC Edit, the ability to set permissions by MARC tag/field so that a library could assign editing tasks for a specific field to an individual user. For example, allowing a user to edit only the 300 field in the MARC record and not be able to edit any other field.
In addition to being controlled by permissions, the ability to allow specific tag/field edits should also be a library or server setting so that a library or consortium can allow or disallow the functionality as a whole.
Revision history for this message
| Galen Charlton (gmc) wrote | #1 |
Revision history for this message
| Mary Llewellyn (mllewell) wrote | #2 |
| Changed in evergreen: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| tags: |
added: cat-marc removed: cataloging editing marc |
To post a comment you must log in.
Given the number of MARC tags that are defined, I think that it might be useful to figure out a way to express the permissions as concisely as possible, possibly through use of wildcards.
Could folks provide some examples of (more-or-less) complete profiles of which tags a given type of cataloger or copy-cataloger would be allowed to edit?
Are there circumstances whereby somebody would be allowed to manage particular subfields but not others within a field?
Is there a need to be able to distinguish between permissions to add a field, modify its contents, or remove it?