[Bug 2496] New: Need more efficient way to edit authority data errors from bib frameworks
http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2496 Summary: Need more efficient way to edit authority data errors from bib frameworks Product: Koha Version: rel_3_0 Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: MARC Authority data support AssignedTo: galen.charlton@liblime.com ReportedBy: debra.denault@liblime.com QAContact: koha-bugs@lists.koha.org CC: rch@liblime.com, jmf@liblime.com, nicole.engard@liblime.com Currently in Koha 3.0 if a bib tag (and specifically the subfield a) is defined to be under authority control via its framework setup, if the user needs to make any changes to the contents of $a to correct typos etc. they must edit the authority directly. Most cataloger's will catch errors when they are in the actual bib record editing it and do NOT want to have to wait until they have made the changes in the bib and saved them to then either a) link to the authority via the MARC tab in bib detail page in staff client to edit or search for the authority itself to edit. It would be a nice enhancement to add an "Edit" link to the search results list that opens up in the new window when a user clicks on "Tag Editor" from an authority controlled tags $a within the bib frameworks and searches for the authority. Clicking on edit should cause the authority framework editor to open in that same search results list window so once the change is made and saved the cataloger can close the window and return to the main staff client window to finish editing the bib. We will need to clearly document that this is the preferred way of making changes to errors in the $a for libraries that link tags to authority controlled data (versus editing directly in the bib framework (bug 2495)) and also to make it clear that the changes will not be reflected when the go back to the bib record and even after they have saved the bibs until merge_authority.pl has completed it's updates. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
participants (1)
-
bugzilla-daemon@pippin.metavore.com