Page History

...

• Discussion regarding new clustering configuration PR:  https://github.com/fcrepo4/fcrepo4/pull/1265

  • It would be interesting to understand the context for this PR

  • Is clustering being used with this new configuration?
• 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: 

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2623

     - 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. 
    • 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.  

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2622

     - duplicate of 2623?  Sounds like it. Jared Whiklo will update the ticket.

  • Jira
    server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2585

    Danny Bernstein working on - sounds like it's almost ready to go. 
• 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 November / 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.  

Actions

•  Danny Bernstein will try to push forward on FCREPO-1262.
•  Doron Shalvi will write up a description of the Fedora URI concerns and post to the Fedora listserv to start discussion.