Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- 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
- Yinlin Chen
- Esme Cowles
- Jared Whiklo
- Andy Wagner
- A. Soroka
- David Wilcox
- Namita Bahulekar
Agenda
- Memento discussion
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- Transactions
- There are a few people who have posted to the mailing list about transactions
- ACTION: David Wilcox will post a follow-up message asking for people to add their use cases to the wiki
- There are a few people who have posted to the mailing list about transactions
- Memento
- Adam: General approval of using Memento and no objections on the mailing list
- We should give people a little while longer to weigh in, and then commit to it
- 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
- Adam: I'll repurpose the existing Memento ticket to be for looking at Marmotta's Memento API in particular:
- Adam: General approval of using Memento and no objections on the mailing list
- Use Cases
- Namita: I would like to retrieve several properties for multiple objects, without having to retrieve the full description of all of the objects separately
- 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
- Aaron: There is a repository with Camel workflows for various kinds of indexing: https://github.com/fcrepo4-exts/fcrepo-camel-toolbox
- In-flight tickets
- FCREPO-1868: Adam: Complicated by use of JCR Session objects, which prompted current transaction use case discussion
- FCREPO-1840: Bethany: Haven't worked on it this week
- FCREPO-1823: Aaron: Working on this slowly, but making progress
- FCREPO-1806: Aaron: More documentation, I'll get to it
- FCREPO-1788: Yinlin: Will wait until Andrew is back next week, will address feedback
- FCREPO-1754: Andy: Need to wrap this up, hopefully in the next week
- FCREPO-1742: Esme: Needs to be rebased, then will talk with Andrew to see if there are any more issues
- FCREPO-1710: Esme: Haven't restarted tests after the break, needs replication
- My scripts are: XXX
- Agenda item for next week
- FCREPO-1694: Aaron: Big project, related to 1312
- FCREPO-1312: Working on this now
- FCREPO-1672: Aaron: We talked about this a few weeks ago – there are a few issues with string literal handling.
- Esme: RDF 1.1 changes the behavior, and we should probably just upgrade and update the tests
- Adam: I don't think anybody is going to be surprised
- FCREPO-1555: Jared: He will get around to it in the next month or so
- There is a PR that needs to be rebased: https://github.com/fcrepo4/fcrepo4/pull/810
- Release candidate
- Aaron: Has anyone tested it?
- 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.
- New tickets
- 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.
- David: I'll take a look at adding a label to identify entry-level tickets
- Yinlin: I just go ahead fixed and submit PR. Took around 10 mins.
- 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.
- Bugs
- FCREPO-1832: Adam: This ticket is for not being able to add ACLs to e.g., the fcr:transform container, to control all transforms
- FCREPO-1830: David: Probably a similar issue with the WebAC implementation
- Jared: I'll take a look at it
- FCREPO-1873: Adam: This issue is renaming a binary – so either of those could be the source of the error
- 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
- I can look at this, but not probably not soon
- 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