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
- IRC:
Attendees
Agenda
Discuss the current use and implementation of IdentifierConverters
- Consider the use of Akka for aync operations
- 4.5.1 Release Planning - when is code freeze?
Bugs are beginning to pile up
Expand |
---|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 30 |
---|
jqlQuery | filter=13122 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
- Fedora Specification updates
- Messaging SPI
- Atomic Batch Operations - name? BatchOps? Bag-o'-Ops? OpSack? AtomicOp?
- CRUD
- Resource Versioning
- Binary Fixity Checking
- Authorization
- ...
Status of "in-flight" tickets
Expand |
---|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 40 |
---|
jqlQuery | filter=13202 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
Ticket Summaries
Please squash a bug!
Expand |
---|
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 40 |
---|
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 | 40 |
---|
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 | 40 |
---|
jqlQuery | filter=13029 |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
|
|
Minutes
Review of current Bugs:
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1887 |
---|
|
- Assigned to Diego Pino Navarro, but he may be busy at present. Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1889 |
---|
|
- We should confirm that the error condition described in this ticket actually exists. A. Soroka will add a comment to this ticket. Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1888 |
---|
|
- Server Errors should include the correct Content-Type (at present, this should be text/plain). As a follow-on, should error responses be RDF? and should Fedora support conneg for errors? Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1884 |
---|
|
- Now assigned to Unknown User (acoburn). Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1882 |
---|
|
- Missing headers. Some parts of this can be merged with FCREPO-1887. A. Soroka will add comments to the ticket. Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1872 |
---|
|
...
- IdentifierConverters:
- The actual implementation, how we provide that service.
- Now it is based on a Guava concept, and what we want is not exactly what it is providing. We should get rid of that and implement exactly what we want.
- It will be a challenge because it is all throughout the code, and the longer it goes, the worse it gets
- The recent move to Java8 (iterators to streams), provides a lot of opportunity to cleanup and make the code base smaller
- What are the convertors? Just a mapping from one world to another world
- Example: Reference to fedora objects (info:fedora/ then the path)
- If you change the hostname, you don't need to change everything
- How to implement? Have an interface that has two function; to, and from
- Guava problem? Syntax vs Semantics -- it's not clear how the "sameness" gets represented
- How to move forward? A. Soroka will pull together some basic contracts, http implementation, and API class.
- Unknown User (acoburn) will open a ticket:
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
...
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1767 |
---|
|
- No activity since November. A. Soroka will ask Nianli Ma for a status update Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1616 |
---|
|
- No activity since November. A. Soroka will ping Esmé Cowles Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1498 |
---|
|
- Unknown User (acoburn) will work this ticket using the touch() method to update jcr:lastModified on referenced nodes, asynchronously (A new ticket will be created to remove the Properties header from emitted Events: Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1945 |
---|
|
)...
- It will be a large change!
- Akka:
- What is it? JVM implementation of the actor model; Highly concurrent, possibly distributed operations
- Other option is thread pools (sharing states and resources between threads is ugly)
- It's a big step, programming model is different and unfamiliar
- Where does it make sense? Things that are async, background jobs
- Before we really kick the tires on Akka, we should identify a couple other use cases
- Should be easier to move forward on this than working on IdentifierConverters
- 4.5.1 Release planning
- Do we want
Jira |
---|
server | DuraSpace JIRA |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
...
...
...
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO- |
---|
|
...
...
...
- take care of this before March 25, 2016
- When is code freeze? After we take care of the above; so March 25, 2016
- Feelings
- Specification updates
- Please read them all, and provide feedback!
- Messaging SPI
- Specifying data that comes out but not the format
- We should support all sorts of messaging protocols
- We don't specify a serialization
- We specify a serialization, or a mandatory serialization
- Use rdf - specify the semantics, not syntax
- fcrepo java client
- Java8 Stream API
- How to become more familiar with it?
Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1818 |
---|
|
- This will be addressed by the maintainer of the OAI project Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1743 |
---|
|
- this is a low priority and will be closed for now Jira |
---|
server | DuraSpace JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | c815ca92-fd23-34c2-8fe3-956808caf8c5 |
---|
key | FCREPO-1559 |
---|
|
- This is expected behavior for SPARQL and not a bug. Unknown User (daniel-dgi) should use an OPTIONAL block for possibly missing properties.
...