Recording is available on: https://drive.google.com/file/d/1WxiyiI1-kCNEIseiL2JAssfmODgpnzsf/view?usp=sharing
Link to the zoom-meeting: https://zoom.us/j/119772606
Link to the wireframes: UX Design Proposed
Link to the discussed document: https://drive.google.com/open?id=167ar6mT-wwaTdrt_-6Ud3Z5npkZ4VFv-icyxCGV_2iQ
|Introduction||@Cult staff met with Filip to discuss the UX proposal. Filip stated in the course of his discussion with @Cult, that four major issues arose that need to be resolved before development can begin on this proposal.|
|Questions and Answers about the UX for MARCcat |
@Cult will do a write up of the outstanding questions, and send out to the group to get feedback and discuss all together during this meeting.
Tiziana shared the screen displaying the UX design proposed. This table is an attempt to encapsulate the discussion:
Attached is a MARC file with two records, sent from Lisa.
“Both of these records are currently in our catalog and are Cambridge ebooks for the same title. The first record in the file, came into our catalog during our migration in 2014 to OLE. The second record was imported in 2016 in a batch that was part of a new collection of Cambridge ebooks we added into our catalog. The import process, which matches on the 035 and 019 fields, should have seen the duplicate OCLC number, but it didn't.
So, this is a duplication that crept into our catalog that we do not want there. Now that I look at these and the model we worked on with Filip, I don't think that model would work the way I would want it to in this case. I think I would need an "OR" type of logic, such as "If a value held in either ($a 035 *OR* $z 035 *OR* $a 019) from one record is the same as a value held in ($a 035 *OR* $z 035 *OR* $a 019) in another record or records, display the results."
A working document that outlines the information @Cult needs from this group will be created. The group members will be asked to contribute to that document.