Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
- Meeting ID: 396 037 251
- Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia
Join fedora-project.slack.com on the "tech" channel
- Self-register at: http://slack.fcrepo.org/
Attendees
- Danny Bernstein
- David Wilcox
- Jared Whiklo
- Peter Winckles
- Daniel Lamb
- Ben Pennell
- Thomas Bernhart
- Mike Ritter
Agenda
- Announcements
- Releases
- fcrepo-migration-validator alpha?
- RC-1 for fcrepo
- Moving off of Jira
- Pilots / Testing
- UTA MySQL Results?
- Pre release short list of bug fixes and improvements
- Any new tickets/issues critical to the release
- Connection Pool move to Hikari
- Your topic
Tickets
In Review
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Notes
- Steering call on Tues. Nothing to report.
- Can Fedora store an arbitrarily large graph?
- In theory it should work. Need to test it
- Single-subject restriction is gone
- Camel toolbox
- Get java client updated
- Pull out osgi related files
- First step getting it out of karaf and into spring and worry about configuration later
- The blueprints could be changed to spring java config
- For against Spring Boot?
- Boot provides a lot of integrations for free (health checks, monitoring, etc)
- How much stuff do we actually need? More simple without?
- Does it need an HTTP interface?
- Sprint scheduled for last week of April
- Migration validator is alpha
- No news from University of Texas - Austin
- Danny working on updating search index
- Should Fedora 3 objects always be migrated to archival groups?
- Archival groups do not model the on disk representation the same as Fedora 3.
- Archival groups do allow resources to be versioned together and for all of the resources to be grouped together on disk
- How much do people care about this?
- When a resource within an archival group is modified, it locks the entire AG to that transaction, which would not happen if the resources were not in an AG
- Archival groups will likely have more versions than an average resource because they are versioned every time any resource they contain is modified.