Skip to content

Instantly share code, notes, and snippets.

@markpbaggett

markpbaggett/report-april-1-2024.md

Created April 1, 2024 12:37
Show Gist options
  • Save markpbaggett/1bcf83f26b09a1e9b75139680392424b to your computer and use it in GitHub Desktop.
Save markpbaggett/1bcf83f26b09a1e9b75139680392424b to your computer and use it in GitHub Desktop.
Download ZIP
Raw
report-april-1-2024.md

Weekly Report - March 25, 2024 - March 28, 2024

Tasks Worked On

  • Student Newspapers
    • Finished Batch 3 of 7
  • Digital Commons and Interoperability
    • Fixed metadata problem that had stopped new digital commons works from being interoperable since August 2022.
    • Brought OneSearch up to date with Digital Commons.
  • Video Migrations
    • Migrated several video collections. In short, we have a mixed bag of success.
    • There is a new EOFErrror that we're now seeing.
    • Reading the traceback and researching online leads me to believe this could partially be our fault.
    • For now, I'm going to break out "large" files from traditional migration processes and simplify the stack down to just web server and file share.
  • Scientist.com and Errors
    • Met with Scientist.com about this and other errors. They too want to simplify this by transferring in to Fedora without importing into Fedora.
    • By this, they mean bypassing the Fedora API and dumping files directly into the attached bucket following the path that Fedora expects (pair tree based on the SHA-1 of the file).
    • I need to write something to do this for all Faraday::TimeOut errors and EOFErrors at least.
    • This requires grabbing the SHA-1 for each file which we don't have currently because we have historically used MD5.
  • Ag Extension DOI Project
    • Researched possible solutions for this project and learned a lot.
    • Beyond this project, I discovered that we can pre-mint DOIs and come back later and update metadata. This would help here but also other processes.
    • Also, talked to Crossref about authorization. Long story short, we can split the service into multiple accounts with one parent account. This is actually their preferred method as they deem it more secure.
    • Beyond that, modelled each of the scenarios they provided at our meeting using the schema.

Thinking About Next Week

  • Student Worker Position
    • Interview and Hire ASAP
  • Migration
    • Create solution for direct file transfers (see above)
  • Student Newspapers
    • Keep ingesting next batch
  • Ag Extension
    • Share findings with Stakeholders
  • Wowza stuff
    • Write salesforce case describing our problem and preferred solution for migration to see if possible.
  • Other Digital Collections
    • Dark archive
    • Merge books into singles where requested
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment