...
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
Discussion regarding: https://github.com/fcrepo4/fcrepo4/pull/1265
- David Wilcox spoke about the AGU Fall meeting that will be in New Orleans in December. If you're interested in attending and representing fedora (essentially taking shifts at a table), contact David Wilcox
- Issues:
- is ready to be merged. Andrew Woods will check in with Aaron Birkland before merging it, though it seems like it's ready to go.Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2623 - there needs to be some work done with converters to have the subject returned correctly for getting the timemap - so that the public facing side is `fcr:versions`, but the internal node name is `fedora:timemap`. Sounds like `fedora:timemap` is being returned right now and shouldn't be.
- a test case needs to be written to test the subject returned when doing a GET on a LDPCv.
- duplicate of 2623? Sounds like it. Jared Whiklo will update the ticket.Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2622
Danny Bernstein working on - sounds like it's almost ready to go.Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2585
- The work on fcrepo versioning is going into a versioning branch right now. Once the basic versioning/memento functionality is there, it will be merged into master.
- 4.7.5
- Incremental Release - Novemeber / December time frame?
- fcrepo-audit - Question is should we continue to support this module or deprecate it?
- Seems like there is general agreement about deprecating it, however, maybe not quite yet until we have a durable solution to replace it with.
- Peter Eichman - talked about the issues they've been seeing. Having the audit messages added in the triple store (via fcrepo-camel-toolbox indexer) is useful and much easier to access audit info that way.
- switched over to indexing triplestore camel route to track audit - will be using that in their production repo starting next week. It is a separate dataset in fuseki.
- thinking about creating audit service that listens to JMS messages and writes to log file(s) - anyone else interested in that?
- One could use the various mature filesystem tools available to manage logs this way (for rotating, viewing, graphing, etc.)
- Their first thoughts on the first pass at this: considering just dumping the JSON messages to disk.
- Might be able to look at fcrepo-camel-serialization tool for inspiration/code
- There are currently two audit capabilities - fcrepo-audit & fcrepo-camel-toolbox triplestore indexing tool.
...