Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Meeting Time

Monday, September 9 at 1 PM Eastern

Attendees

  • Emily Lynema (Indiana)

  • Joshua Westgard (UMD)

  • Jon Cameron (Indiana)

  • John Merritt (Louisville)

  • Jason Coleman (NEC)

Zoom Link

https://iu.zoom.us/j/84620830059?pwd=bWo3R081M3BtaytFMjZnS0FzQkd2dz09

Agenda/Notes

  • Does it work to move our monthly meeting from 2nd Monday of the month to 3rd Monday of the month to accommodate UMD folks?

    • No conflicts

    • Emily will follow up on email / Slack

  • Use cases for tools to update metadata in bulk in Avalon

    • Josh: UMD has advocated for this

      • For both paged and streaming media, do everything in batches. Don’t do one by one item creation b/c don’t have staffing to do that.

      • Import things in bulk, and subsequently to update in bulk using the same process.

      • Batch import allows you to re-upload items that failed to upload based on the ID.

      • First download the metadata as a CSV, make changes, and then reload. Download must have identifier saying which item.

      • How to know which fields to overwrite? In paged media repository, which talks directly to Fedora, it pulls down the RDF, does a diff, and updates only the changed fields

      • Ideas about how to record metadata change over time, and want to be able to adjust. For example, their permalink is Handle; have put Handles on all objects in Avalon. When added that feature, had to go back and retroactively add them to items already in the system. Because they couldn’t do that, they added functionality to Avalon to mint new Handles for items that didn’t have one.

    • Jason (NEC)

      • Ex: being able to come up with a series in Avalon. Have several concert recordings that are in a particular series. Need to change a concert from concert series A or concert series B. This would involve updating title, contributor, or statement of responsibility.

      • Spreadsheet type system would probably work for them, too.

    • John M (Louisville)

      • not at the point they need bulk editing yet

    • Jon C. (IU)

      • ex: updating Rights Statement for a group of records that have been reviewed for copyright; adding content warning to summaries

      • also suggested the idea of downloading a set of items, editing in a CSV, and re-uploading

  • IU is proposing to make Subjects o the media item page in Avalon hyperlinked so that users can click on a Subject to match to a search for other items with that Subject.

  • IU also proposed making Publication Date no longer a required field.

  • summation of Avalon user survey (slides)

  • Future agenda items?

    • Potential conversation around upgrade process for institutions that have been using Avalon for awhile (how to handle code customizations, etc.)

  • No labels