| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dev:proposal:authorities [2010/07/15 04:07] – Expand on the authority record selection requirements dbs | dev:proposal:authorities [2022/02/10 13:34] (current) – external edit 127.0.0.1 |
|---|
| |
| * Mike committed [[http://svn.open-ils.org/trac/ILS/changeset/16816|r16816]] to implements optional (controlled by a global flag) bib-authority linking via repeatable $0 subfields. The set of controlled fields will likely need to be expanded and adjusted, but this commit implements the same set that is used by the Validate button in the MARC Editor. The agency code in the $0 of the bib and the 035$a of the authority record are both ignored, and only the numeric code (the ''authority.record_entry.id'', forced into the authority record) is used. For example, given the subfield ''$0(CONS)1234'' in bibliographic record ID ''9876'', ''1234'' will be inserted into the ''authority'' column of the ''authority.bib_linking'' table and ''9876'' will be inserted into the ''bib'' column to track the authority-to-bib relationship. | * Mike committed [[http://svn.open-ils.org/trac/ILS/changeset/16816|r16816]] to implements optional (controlled by a global flag) bib-authority linking via repeatable $0 subfields. The set of controlled fields will likely need to be expanded and adjusted, but this commit implements the same set that is used by the Validate button in the MARC Editor. The agency code in the $0 of the bib and the 035$a of the authority record are both ignored, and only the numeric code (the ''authority.record_entry.id'', forced into the authority record) is used. For example, given the subfield ''$0(CONS)1234'' in bibliographic record ID ''9876'', ''1234'' will be inserted into the ''authority'' column of the ''authority.bib_linking'' table and ''9876'' will be inserted into the ''bib'' column to track the authority-to-bib relationship. |
| | * Dan committed server-side support for ensuring that when bibliographic records merge, the bib value in the authority-to-bib linking table will be updated accordingly [[http://svn.open-ils.org/trac/ILS/changeset/16935|r16935]]. |
| **TODO**: Add actions to clean up ''authority.bib_linking'' when authority records are merged or deleted. | |
| |
| ==== Syncs ==== | ==== Syncs ==== |
| ==== Highlight controlled fields ==== | ==== Highlight controlled fields ==== |
| Highlight in the user interface when an uncontrolled field is validated as a controlled field and linked to a specific authority record (this presupposes that we teach the "Validate" button to add the appropriate $0 to the field when a matching authority is found) | Highlight in the user interface when an uncontrolled field is validated as a controlled field and linked to a specific authority record (this presupposes that we teach the "Validate" button to add the appropriate $0 to the field when a matching authority is found) |
| |
| ==== Simplify authority record selection ==== | ==== Simplify authority record selection ==== |
| Improve authority selection interface during bibliographic cataloguing (such as the ability to invoke a browse list, perhaps; also to prevent cataloguers from choosing a See From tracing, etc). | Improve authority selection interface during bibliographic cataloguing (such as the ability to invoke a browse list, perhaps; also to prevent cataloguers from choosing a See From tracing, etc). |
| |
| * Part 1: in the current contextual display of the selected authority record, the cataloguer is able to pick as many subfields as they like from the entire record. This is too much information. Subfields outside of the 1* and 5* fields should be disabled, possibly even hidden, in this view. | * Part 1: in the current contextual display of the selected authority record, the cataloguer is able to pick as many subfields as they like from the entire record. This is too much information. Subfields outside of the 1* and 5* fields should be disabled, possibly even hidden, in this view. |
| * Part 2: enable the cataloguer to generate a browse list based on the authority browse list support that Mike added (via URLs like ''http://localhost/opac/extras/browse/marcxml/authority.author/CONS/Mulder''). Ideally the browse list axis (''authority.author'', ''authority.subject'', ''authority.title'', ''authority.topic'') and search term could be populated from the chosen uncontrolled term. The display could be generated from the MARCXML browse list using something like: <code javascript> | * Part 2: enable the cataloguer to generate a browse list based on the authority browse list support that Mike added (via URLs like <del>''http://localhost/opac/extras/browse/marcxml/authority.author/CONS/Mulder''</del> ''http://localhost/opac/extras/startwith/marcxml/authority.author/CONS/Mulder''). Ideally the browse list axis (''authority.author'', ''authority.subject'', ''authority.title'', ''authority.topic'') and search term could be populated from the chosen uncontrolled term. The cataloguer should then be able to select the entry they want to apply to the previously focused field in the MARC editor. The display could be generated from the MARCXML browse list using something like: <code javascript> |
| dojo.query('record'); // to grab the list of records, then for each record: | dojo.query('record'); // to grab the list of records, then for each record: |
| dojo.query('datafield[tag^="1"]'); // to grab the controlled list of subfields from each record | dojo.query('datafield[tag^="1"]'); // to grab the controlled list of subfields from each record |
| dojo.query('datafield[tag="901"] subfield[code="c"]'); // to grab the authority record ID | dojo.query('datafield[tag="901"] subfield[code="c"]'); // to grab the authority record ID |
| </code> The same sort of basic interface could be used to generate a list of authority records upon which the MARC editor could be invoked. | </code> The same sort of basic interface could be used to generate a list of authority records upon which the MARC editor could be invoked. //Looks like BibTemplate to me ... ;)// |
| |
| |
| |
| Implementation thoughts: largely cut and paste from the existing metabib indexing framework. | Implementation thoughts: largely cut and paste from the existing metabib indexing framework. |
| |
