2018-07-30 MARCcat Subgroup Meeting Notes

1A. Original Cataloging -

1. 1. Tiziana: Will you work in OCLC? @Cult can use clarification on how this works
   2. Laura: Added this use case. She thought Cornell's workflow is significantly different, so wanted to be sure their workflow is taken into account at some point. At Boulder, for original or copy, they begin in the OCLC database. All original cataloging is done in OCLC first. Only after that are the records brought into the local system. At that point, local notes and local admin info is added. Editing of bibliographic data would not be done in the local system.
   3. Mary said this is the similar procedure at Alabama.
   4. Laura - Important point - bibliographic data is not edited in local system at Boulder. She thinks Cornell may create the record in the local system then export it into OCLC.
   5. Tiziana - Some sort of API is needed to update FOLIO - starting from OCLC to accommodate libraries that catalog mainly in OCLC, then bring the record or records into FOLIO.
   6. Laura added that their main authority work is done in OCLC also.
   7. Tiziana - It could be useful to have a brief demo of this workflow, so they can see how libraries that work in OCLC do so. This is not a common workflow in Italy or with @Cult's customers. Action - Schedule a demo of this workflow. Lisa will share next Monday, this workflow, with other members stating their differences from this process. 1) start from OCLC 2) Each work shares work
   8. Ann-Marie - Is there value in having a "button" for a single record import. Anything we do for batch will be usable for single records. Is that efficient for single records.
   9. Tiziana - Many of these use cases touch upon the batch import import aspect of FOLIO. It would be useful to have a clear understanding of batch import. What would happen if a record is loaded into MARCCat, what happens in Inventory and vice versa? These questions arise when thinking about these use cases.
   10. Laura - Single vs. Batch - Why would single record be treated different? In their current system, Sierra, they can push a record from OCLC into their system.

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) -