...
- A. Soroka
- Unknown User (acoburn)
- Unknown User (escowles@ucsd.edu)
- Bethany Seeger
- Nick Ruest
- Andrew Woods
- Jared Whiklo
- David Wilcox
- Osman Din
- Yinlin Chen
- Michael Durbin
- James R. Griffin III
- Aaron Birkland
- Stefano Cossu
- Kevin S. Clarke
Agenda
Retiring m2.duraspace.org
- Server-managed Premis predicates:
- ModeShape and many-child-nodes... almost perfect: https://github.com/ModeShape/modeshape/pull/1459
Bug Prioritization
Expand Jira server DuraSpace JIRA jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 - F4 GitHub Organizations - "Becoming an fcrepo4-exts project"
- WebAC update
- Hydra and Islandora involvement?
- Notice: API Extension Architecture call tomorrow (design)
...
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
Retiring m2.duraspace.org
- Hosts a number of Maven artifacts that Fedora 3 needs
- We would like to retire it
- One approach: retire very soon and offer a script and JAR files to build the latest version of Fedora 3
- Another option: Continue maintaining the server (not very appealing)
- Someone else could stand up the server on their own infrastructure and redirect the DNS
- We could send a post to the mailing list asking if anyone wants to maintain the server
- There are probably very few people interested in building Fedora 3 vs. just using the installer
- For these people, will Andrew’s build script work as an option?
Server-managed PREMIS predicates
- There are some server-managed predicates in Fedora 4 now
- In some cases users want to manage their own PREMIS properties but they are currently immutable
- Should we stop using non-Fedora predicates for server-managed properties?
- We have to reserve some LDP properties, though many can be updated via SPARQL-Update
- In the case of PREMIS/fixity, should we (1) use a Fedora namespace, or (2) continue to use PREMIS but allow the properties to be mutable?
- Recommendation: Investigate allowing fixity-related properties to be user-modified
- Longer-term: Investigate using a server-managed Fedora namespace instead of PREMIS
ModeShape performance issue with many child nodes
- This issue has been addressed by the ModeShape community by creating a new node type
- The only issue is that this new node type won’t work with versioning
- Might be possible to have the root node be of this type and all other nodes be of the normal (versionable) type
- This mix of versionable and non-versionable containers might be cumbersome
- Need to add some concerns as comments on the PR
- We need to run new scalability tests with these updates
- The only issue is that this new node type won’t work with versioning