Review

As you work on your collection branch, be sure to Commit your changes and Push regularly. Note, the first time you push a new branch to GitHub, the message from GitHub Desktop or VS Code will be about “publishing” your branch–this will make it available on GitHub. Use meaningful commit messages to ensure collaborators (and your future self) understand what you were doing.

Before Submitting Your Collection:

• Checking your metadata:
  • Make sure format, type and display_fields are filled in and assigned appropriately. Does an image have text that would be beneficial to be keyword searchable? If so, make sure these items are assigned as documents and the files are PDFs with a layer of OCR.
• Check your formatting:
  • Make sure all of your multi-valued fields (subject, author, etc.) use a semi-colon to separate values
  • Strip any leading or trailing white space
  • Make sure your CSV is exported with UTF-8 encoding (default of Google Sheets but not Microsoft Excel)
  • Check that your filenames match your media, including file type variations (jpg vs. jpeg)
• Generate your site on your using your local server, check links and all pages to ensure features are working as expected and all items are displaying.

Do not hesitate to reach out for help debugging issues or if you need a large amount of images to be converted to PDF with OCR!

Publish

Once the collection is ready, submit it to the CDIL team via the Collection Update Form.

Collection Update Form

The Digital Projects Manager and Digital Initiatives Librarian will prep it for publication:

• Merge any updates from main if necessary.

• Ensure objects and metadata are fully prepped and organized (CDIL Team):
  • Derivatives generated.
  • In archive drive for preservation, with README.
  • On libobjects for access.

• Ensure “config-search-index.csv” is correctly configured.

• Test locally.

• Build and deploy to live web location.

• Once the new collection is online (but unlisted), share the link and blurb out to DC team with a one week timeline for testing and feedback. Feedback form.

• Fix any issues, editing, or ideas that come up from DC-QC

• Add to Search Sources, opt into central-search, and redeploy.

• Add an entry to the Digital Collection Tracking spreadsheet.

• Add to collection master list, publish on Collection browse page

• Ensure Digital Collection Tracking spreadsheet is updated, moving collection from “current” to “finished” tab. Record launch date so that we can check on analytics for referrers and spike in use.