...
- Is the retention byte (008/12) going to be updated also?
- Are the ReCAP commitment for specific items owned at that time, or are new acquisitions (such as subsequently received issues of the same journal) also going to be committed?
- Whose responsibility is it to develop/document/communicate policies and workflows on manual creation, maintenance, etc to make sure conflicts in coding don’t develop in future?
- Is there contention between previously entered 583 fields and current fields? This needs analysis once records have been updated.
- Are there other retention commitment scenarios, shared or local, that we need to accommodate in our use of these item and holdings fields?
- What is the intended workflow for items that are marked lost or missing? Do these need to be sent to collection development staff?
- Is work on this a higher priority than Google scanning processing or the creation of the metadata file for Ivies Plus?
- What is the workflow to use is a committed item is replaced with a new copy (for lost or damaged items)?
Impact on Ongoing Workflows
- Staff will need training to look for the commitment statement before withdrawing items.
- Workflow documentation would need to be developed for cases when withdrawing a previously committed item occurs.
- Workflows will need to be developed to add or update item data and holdings 583 notes (including, potentially, $3) when new commitments are made.
Timeline for ReCAP
- Approve Recommendation
- Creation of itemized sets for 4 million items (1 week)
- Update items identified for 4 million items (Allison to get projection of 10,000 items throughput)
- Identify linked holdings and update with 583 field (Allison to get projection of ~10,000 holdings throughput)
...