At the MARCcat working group meeting 7/23 is was decided to document typical workflows for catalogers - experienced, less experienced cataloguers etc. The intention with this, is for the atCult team and the UX designers to learn more on how the FOLIO libraries catalogue MARC records in their existing systems today, and typical environments like OCLC, and Union Catalogues.

Tiziana Possemato and Annalisa Di Sabato are planning to do a demo of WeCat (MARCcat) at one of the upcoming MM-SIG meetings - e.g. August 1, 2018 (TBD). The demo would be quite similar to the demo at the MARCcat subgroup meeting - see link to the recording at the meeting minutes

All subgroup and MM-SIG members: please add any relevant use cases. In the table the documentation of the usecases have been categorized, but feel free to ad many more categories. If a use case is already represented, then add your name and library, if you have exactly the same workflow process. Please fell free to add any additional details.

It might work well to add a link to a document with screen dumps.

Use case (brief)

Use case description

Region (US, Sweden, Germany ...)

Submitted by


Link to document
Experienced cataloguer:

1original catalogingCreate record in OCLC; verify/update/create authority records as needed & control headings in OCLC record; bring record into local system (would we bring into FOLIO via MarcCat or could we import directly into FOLIO?); add/edit administrative data such as cataloging level, cataloger initials, cataloged date; create holdings/item recordsUS

2original or copy cataloging, local notes needed for Special CollectionsSame as above, except we would need to edit the record in MarcCat to add local notes (such as provenance)



Newly hired cataloguer:






Copy cataloguing:






Other processes:
10outsourced authority control/record updates-- bibliographicWe send monthly files of records to a vendor who adds some fields (such as 33x) if needed and also matched access points in bib records with authority records. We then receive bib records back with updated fields and reports with unmatched access points. Records are reloaded.
Laura Wright

11outsourced authority control/record updates-- authorityWe receive quarterly files of authority records that correspond either to new (to our database) access points or changed access points. These files, when loaded, trigger an automatic authority control process that acts on our bibliographic records (locally) and updates access points, matching on 4xx and 1xx fields. Changes to access points would need to occur in MarCat.
Laura WrightThere is also a lot of manual searching, matching, and updating that has to be done based on reports of unmatched headings. This work would also need to be performed in MarcCat.