dev:proposal:authorities
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:proposal:authorities [2010/07/15 03:47] – Formatting dbs | dev:proposal:authorities [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 17: | Line 17: | ||
* Mike committed [[http:// | * Mike committed [[http:// | ||
- | + | | |
- | **TODO**: Add actions to clean up '' | + | |
==== Syncs ==== | ==== Syncs ==== | ||
Line 33: | Line 32: | ||
==== Add an authority in the flow ==== | ==== Add an authority in the flow ==== | ||
Make it easy to manually add an authority during bibliographic cataloguing, | Make it easy to manually add an authority during bibliographic cataloguing, | ||
+ | * Thought: Add **Add this as an authority** as another contextual option in the MARC editor - which would: | ||
+ | * Create the new authority record based on the currently highlighted field | ||
+ | * Grab the record ID for the new authority record | ||
+ | * Add the appropriate $0 subfield using the are.id to the currently highlighted field | ||
+ | * Also want an **Add this as an authority and edit** option that would invoke the authority record MARC editor to allow fine-tuning of the authority MARC. | ||
==== Fix fixed fields for authorities ==== | ==== Fix fixed fields for authorities ==== | ||
The current MARC editor does not know about any kind of MARC other than bibliographic records. Teach it to properly handle authority records so that the fixed fields don't look insane. | The current MARC editor does not know about any kind of MARC other than bibliographic records. Teach it to properly handle authority records so that the fixed fields don't look insane. | ||
+ | * Dan committed [[http:// | ||
==== 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 " | 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 " | ||
- | |||
==== 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 2: enable the cataloguer to generate a browse list based on the authority browse list support that Mike added (via URLs like < | ||
+ | dojo.query(' | ||
+ | dojo.query(' | ||
+ | dojo.query(' | ||
+ | </ | ||
==== Delete authority record ==== | ==== Delete authority record ==== | ||
Line 54: | Line 66: | ||
Implementation thoughts: largely cut and paste from the existing metabib indexing framework. | Implementation thoughts: largely cut and paste from the existing metabib indexing framework. | ||
- |
dev/proposal/authorities.1279180047.txt.gz · Last modified: 2022/02/10 13:34 (external edit)