...
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
Attendees
- Unknown User (acoburn)
- Bethany Seeger
- A. Soroka
- Yinlin Chen
- Esme Cowles
- Jared Whiklo
- Andy Wagner
- David Wilcox
- James R. Griffin III
- Andrew Woods
- tamsin johnson
- Benjamin Armintor
- Namibia Bahulekar
- Allen Flynn
- Katherine Lynch
Agenda
- How many child resources do I have?
Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1880 - Modeshape 5.x update
- Next steps: Fedora specification
- Service detailing
- Alt implementation verification
- TCKs
- Spec writing
- LDP and other standards coordination
- MySQL migration testing
- Fedora backup: documents_000001.bin.gz<insert your topic here>....
Status of "in-flight" tickets
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Minutes
Child Resources
- Assumption: When you make a request on a container you should know how many children that container has
- Fedora should provide this information
- Going into a paging scenario with this information would be nice
- The current code iterates over all the children and counts them
- This can be a performance issue with very large numbers (millions) of children
- Instead of dynamically creating this count, we could maintain a property that gets updated when children are created or removed
- Right now, we don’t have good information on when children are created via federation
- In general, it is difficult to know how many children are in a federated file system period. This should not stop us from making in-repository storage perform better
- There is a child count property we could use - it does not indicate whether those children are in repository or federated storage
- Could we use a listener to listen for federated changes and update the property in Modeshape?
- Record number of children, bytes, and a timestamp and us a TTL to update at periodic intervals
- Not sure if we could override the way the federated filesystem gets queried for its contents
- We could pursue one solution for in-repository content and another solution for federated resources
- Both solutions should use and maintain the same property
- Action: Create a separate ticket for each solution
ModeShape 5 Update
- There will probably be a couple more 4.x releases
- ModeShape 5 is projected to be released in March
- We will want to install and test this release with Fedora 4 when it is available
Fedora Specification
- A message regarding the API spec was sent to the Fedora community yesterday
- We want to clearly define what Fedora is in a specification
- The proposal includes API and SPI services and WebAC for authorization
- An effort is currently underway to detail each of the services
- We want to have a number of alternate implementations to verify that the API is independent of any particular implementation
- We need to have TCKs that progress alongside the specification work
- Who will volunteer to take responsibility for the service pages on the wiki?
- What will the final spec look like and where will it live?
- It should be in the same form as the other W3C recommendation documents that are out there
- It should not just live in GitHub or on a wiki
- W3C Respec for authoring: https://www.w3.org/respec/
- This is difficult to do in the wiki. Probably still difficult in GitHub
- Maybe a Google Doc?
- Useful but will not help produce a spec doc
- Are GitHub issues a barrier?
- Could we use JIRA instead since we already have a running instance?
- Maybe a Google Doc?
- Action: As a starting point we will use a Google Doc but transfer to something else if need be
MySQL Migration Testing
- There are some documented issues with LevelDB
- Need to migrate backup dump from LevelDB to few Fedora repo with MySQL to test
- Action: Yinlin Chen will test a migration from LevelDB to MySQL
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1906
Fedora Backup
- There is no guarantee of order of resources in a Fedora backup dump