bib source should be included in the 901 field
Bug #1307553 reported by
Galen Charlton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
It might be handy of the maintain_901() trigger included the bib source code in a subfield in the 901. This would allow:
- more directly expressing bib source as a match point for import
- the option of easily indexing the bib source as a searchable attribute
- providing a hook for additional record-handing logic (e.g., for managing electronic resource records)
Note that a related issue is bug 1178377, which proposes to add the bib source to unapi.bre output for use in TPAC styling. This is orthogonal to this wishlist.
Original idea by Mike Rylander
Evergreen master
Changed in evergreen: | |
importance: | Undecided → Wishlist |
tags: | added: pullrequest |
tags: | added: needsreleasenote |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm wondering what subfield would be best, and for all schemas or just biblio?