Recording is available on: https://drive.google.com/file/d/19B97LZiuU0cnlncaKSteAfaHnaeJx5vR/view?usp=sharing
Link to the zoom-meeting: https://zoom.us/j/836537290
Goal: Use cases analysis and discussion (# 1- 3)
|Use Cases Review||Tiziana Possemato|
1A. Original Cataloging -
1B - (Jason Kovari's use case) - Charlotte - It would be useful to have all contributors of the use cases to attend a meeting about this, so everyone can explain their use cases to make sure it is clear to Tiziana. Tiziana will create a Doodle poll on the MM channel to see when everyone can participate in a feedback meeting. Tiziana has specific questions.
1C - (Felix Hemme's use case) - May be good to have a demonstration of this. Ann-Marie thinks it may be parallel to the OCLC workflow. The fact they use a different database for journals , may impact the batch import development. Ann-Marie thought this may be covered in batch loader use cases.
2A - Original or copy cataloging, local edits to record (Laura Wright) - Primary work is done in OCLC, but local fields will be added after the record is brought into local system. What happens when a record originally created in OCLC is edited locally? Does that OCLC record get updated? Laura - if edits are being made to the master record, that will apply to anybody, the record in OCLC is updated, and the local records would be updated, but manually. However, if the edits are only locally applicable, the record in the local database will change, but the OCLC record will not change. Tiziana is wondering if records are ever edited locally and pushed to OCLC. Laura suggested asking Jason if that scenario can exist.
If a library updates a master record in OCLC? What happens to other libraries that use this master record. Answer - OCLC offers the option to receive a file of records that have been updated. See use case #28.
3. Original or copy cataloging, local edits to record (Natascha Owens use case) - Tiziana understands correctly that local changes can be made that do not need to be made to the OCLC database
4. Simple edits (Natascha Owens use case) - Roles and privileges that can be defined in MARCCat will be defined and demonstrated. However, some permissions currently set in WeCat may need to change to accommodate the different needs of the libraries. WeCat's authorization levels are related to category types. They are open to other suggestions. The need was summarized by Ann-Marie as the need for a "light-weight editing screen."
5. Merging Authority Records (Natascha Owens use case) -
- Post question on the wikis.