Recording is available on:
Link to the zoom-meeting:https://zoom.us/j/402140608
Link to the wireframes:
Link to the discussed document:
|MARCcat UX/UI analysis |
Tiziana Possemato, Paul Mouland
Tiziana introduced Paul, who has worked for at Cult as a consultant for 20 years.
Discussion about MARC validation/tag tables by Paul Mouland. Paul demonstrated the main tag table for Amicus. Amicus is the library product first developed at the National Library of Canada and owned by at Cult.
Today's MARCcat meeting discussed interactions between MARC21 documentation and local tag tables. What kind of help do we want to display to users of the MARCcat tool? I was asked to show some screenshots of my local Voyager system, which I'm not exactly recommending, just demo-ing here.
A little bit of a bib, with my cursor on the 260 line of an old and cruddy record:
See the lower left corner? The words "Publication, Distribution, etc. (Imprint)" are not being pulled from the MARC21 document at http://www.loc.gov/marc/bibliographic/bd260.html, but rather from the local tag table, which has cut-and-pasted the MARC21 guidelines.
If I put my cursor on the 260 $b and hit a function key, I get a table of valid values:
This list also is pulled from text in our local tag tables. Notice that we are carrying value "d" for our legacy data, outside of current MARC21.
And for a local tag, also driven by the local tag table, let me show our 852, not the same as the MARC21 852:
Because of the way our tag table integrates with our editor, when a user puts their curson on the 852, they get the quick help in the lower left corner of their screen that says "Local call number, used for bulk import of shelf-ready records" and when they can't remember the subfield codes, they can display valid values using the function key.
I like the idea of linking out from MARCcat to MARC21 documentation, but I do also like the little quick-help tags. I might add that errors in the local tag tables are rather easy to expose with this method, which is a good thing, if occasionally embarrassing.
Also, here's some of the conditional logic for generating format types at the very top of the record that I was inaccurately gesturing towards and which I believe Paul also alluded to:
Nothing surprising but it is a huge pain to change anything other than a new value in the fixed fields.
|Colin Van Alstine|