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 3 Current »

\uD83D\uDDD3 Date

@9am Eastern

\uD83D\uDC65 Participants

⭐ indicates note taker

\uD83E\uDD45 Goals

  • Updates on progress for ongoing development work

\uD83D\uDDE3 Discussion topics

Item

Welcome

Updates:
Pairtree paths

Default admin set IDs

Will FileSet/File IDs be preserved in migration?

Performance Testing

What work remains?

Wrap Up

Next meeting:

Next note taker:

Notes

Updates

  • Pairtree Paths

    • PR merged in valkyrie to support, but hasn’t been released yet

    • Hyrax unblocked from merging PRs, needed CI updates after switching to gh actions

  • Default admin set IDs

    • PR to change the default admin set id to not contain non-URL safe characters was merged

  • Will FileSet/File IDs be preserved in migration?

    • If there is an existing id it gets added as an alternate ID to the fileset, so they can be looked up by the old id in queries, but there is probably more work that needs to be done

    • Emory - they have been needing to do more work than expected related to alternate IDs as part of their fedora 3 migration. Needed to define their own custom NOID scheme rather than defaulting to UUID.

      • Seems like this is resulting in creating an extra fedora resource for the alternate ID.

      • if you go string ID route in valkyrie, you’re responsible for any kind of pair tree setup, fedora only does this if it is totally in charge of creating the ID.

    • Going to add sirenia to gh action workflows soon, to help catch issues like this.

  • Emory Updates

    • When persisting resources to fedora 6, trying to persist FITS data, needed to do some work to use predicates that aren’t example.com. Apparently valkyrie uses this prefix for properties if they don’t have a mapped predicate URI.

      • Daniel thought this had already been set up for all the hyrax predicates

  • Questions for Rob and migration teams

    • Could have a separate meeting, or just join the hyrax interest call (next is july 10 at 11:30est, but might be vacations involved).

    • Emily interested in a deeper dive in what actually happens in the Frigg migration tool.

  • Performance Testing

    • Julie almost through testing all of the cases, but has had some parts fail, so still trying to get through some of them

    • Nurax running fedora 6 expected to be up as a part of the next hyrax release

    • No one has done test case of 5000 files

Wrap up

  • Next meeting - July 26, 9est

✅ Action items

  • ✅ Check on if more work needs to be done to cover all the predicates from hyrax so that they get persisted to Fedora with a real URI, particularly FITS ones.

  • No labels