A nurax-style environment would be helpful - in the works
Issues w/ Hyrax + Fedora 4 start around 4K AF objects in a collection, or 100 filesets in an object (which is around 40K+ objects in Fedora). Can force the issue by limiting the amount of memory that Fedora has.
There is a test script that can be shared.
Can use Bulkrax to script up performance testing
Bulkrax is mostly ready for use with Valkyrie
The representation of fiesets as being part of the work node exacerbates the performance issue
Group should revisit the charter and discuss if changes are necessary given the progress in implementation.
Is migration in-scope-able? SoftServ has a metadata migration adapter (No files, yet).
Largest questions are around representation of binaries in Fedora
Another issue is around pairtree id problem.
Another future topic is Archival Groups
How or if they are created may become a configuration option in the adapter.
Performance differences between atomic and archival versioning? On Dan’s TODO list.
Now working against bare metal, will be working with TACC.
Fedora UI, analytics, user admin are also going to get an overhaul.
How is provenance tracked? It’s not, but that use case has come up for Fedora before.
Hyrax interacts with Fedora as one, anonymous user
Fedora provides a log of actions that could be used as an audit log.
To track provenance effectively, Hyrax would need to change.