Differences

This shows you the differences between two versions of the page.

--- dev:proposal:authorities [2010/07/15 06:00] – Mention updated merge support dbs
+++ dev:proposal:authorities [2022/02/10 13:34] (current) – external edit 127.0.0.1
@@ Line 44: / Line 44: @@
 ==== 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)
 ==== 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).
   * 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 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>
+  * 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('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
-</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 ... ;)//
@@ Line 67: / Line 66: @@
 Implementation thoughts: largely cut and paste from the existing metabib indexing framework.