Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees 

Agenda

  1. Memento discussion
  2. Status of "in-flight" tickets

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3.  

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  2. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

  1. Transactions
    1. There are a few people who have posted to the mailing list about transactions
      1. ACTION: David Wilcox will post a follow-up message asking for people to add their use cases to the wiki
  2. Memento
    1. Adam: General approval of using Memento and no objections on the mailing list
      1. We should give people a little while longer to weigh in, and then commit to it
    2. Esme: I think it would be good to look at Marmotta and look at how they are implementing Memento, and follow the same patterns if possible
      1. Adam: I'll repurpose the existing Memento ticket to be for looking at Marmotta's Memento API in particular:  FCREPO-1275 - Getting issue details... STATUS
  3. Use Cases
    1. Namita: I would like to retrieve several properties for multiple objects, without having to retrieve the full description of all of the objects separately
    2. Adam: That's really a bad fit for a REST API, but that would be easy to do with a SPARQL query with a triplestore
    3. Aaron: There is a repository with Camel workflows for various kinds of indexing: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox
  4. In-flight tickets
    1. FCREPO-1868: Adam: Complicated by use of JCR Session objects, which prompted current transaction use case discussion
    2. FCREPO-1840: Bethany: Haven't worked on it this week
    3. FCREPO-1823: Aaron: Working on this slowly, but making progress
    4. FCREPO-1806: Aaron: More documentation, I'll get to it
    5. FCREPO-1788: Yinlin: Will wait until Andrew is back next week, will address feedback
    6. FCREPO-1754: Andy: Need to wrap this up, hopefully in the next week
    7. FCREPO-1742: Esme: Needs to be rebased, then will talk with Andrew to see if there are any more issues
    8. FCREPO-1710: Esme: Haven't restarted tests after the break, needs replication
      1. My scripts are: XXX
      2. Agenda item for next week
    9. FCREPO-1694: Aaron: Big project, related to 1312
      1. FCREPO-1312: Working on this now
    10. FCREPO-1672: Aaron: We talked about this a few weeks ago – there are a few issues with string literal handling.
      1. Esme: RDF 1.1 changes the behavior, and we should probably just upgrade and update the tests
      2. Adam: I don't think anybody is going to be surprised
    11. FCREPO-1555: Jared: He will get around to it in the next month or so
      1. There is a PR that needs to be rebased: https://github.com/fcrepo4/fcrepo4/pull/810
  5. Release candidate
    1. Aaron: Has anyone tested it?
    2. David: We probably need to bring this up again to get people to test the RC.  If no one has tested this, then we should probably not release it next week.
  6. New tickets
    1. FCREPO-1874: Adam: This is a problem for several exceptions.  Also, a good ticket for new developers since it doesn't require extensive knowledge of JAX-RS, etc.
      1. David: I'll take a look at adding a label to identify entry-level tickets
      2. Yinlin: I just go ahead fixed and submit PR. Took around 10 mins.
  7. Bugs
    1. FCREPO-1832: Adam: This ticket is for not being able to add ACLs to e.g., the fcr:transform container, to control all transforms
    2. FCREPO-1830: David: Probably a similar issue with the WebAC implementation
      1. Jared: I'll take a look at it
    3. FCREPO-1873: Adam: This issue is renaming a binary – so either of those could be the source of the error
      1. Esme: The API has separate methods for renaming vs. moving to a different container, so we may need to check for the destination being in the same container
        1. I can look at this, but not probably not soon