Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Unit: Batch Processing and Metadata Management

Date last reviewed: August 2022 April, 2023

Date of next review: August 2023April 2024

...

A. Inquiry from Stakeholder and Ingest of Data

  1. Request should come to the Head of Automation (jrc88). It may be communicated in a meeting or in an emailbulkload@cornell.edu if it is being submitted by email (preferred unless it is complex enough to warrant a meeting). Head of automation will triage the requests in LibAnswers.
  2. Examples of information to be supplied by the stakeholder include:

...

  1. Staff member reviews the pertinent information and seeks additional information and feedback, as needed.  
  2. For MARC record loads, staff member will review process with Automation head and vet the finished records with the Original Cataloging Supervisor or other appropriate original cataloger for correctness of the records, noting any changes required.   After consultation, a decision is made whether the project requires scripting from CUL-IT programmer or can be handled with the tools available for staff.

...

C. Documentation of Proposed Specification/ Process

  1. Whether or not scripting by IT is needed, a A specification document will be created in the CUL Tech Services Working Group detailing all pertinent information and the processing steps required.If a script is required, automation head will generate tickets for IT staff in appropriate context (JIRA or GitHub depending on the project).

...

 D. Analysis and Finalization of Proposed Process

  1. When script or MARCEdit task is completed, testing is done by Automation Staff Member in the test instance of FOLIO and results are verified as correct by appropriate staff and stakeholder(s). Decision to make the script a Prefect flow is based on the frequency and regularity of data being present that needs to be transformed and ingested into FOLIO or frequency data needs to be reported.
  2. Stakeholder who made request will be informed when processing or initial record load is completed.
  3. If appropriate, stakeholder or other designated staff member will be trained to use this process on future records.