Meeting 02 - 2016-12-07

• 12pm ET

1. https://github.com/fcrepo4-labs/fcrepo-import-export/pull/48

   Should we support mapping repository paths, not just host/port

   Esmé Cowles - This ticket came out of integration test for round tripping, export and import into a different directory. 

   We had some allowance for different hostname ports, but base URI and everything else must be the same. At least the base URI could be modified in case of changed deployment.

   While doing that Hydra already has various sub-directories, so that could be great. But it brings up issues. How do you handle if you export a resource, but not any linked resources.

   Is it a requirement to be able to export a resource/tree of resources and then import it into a different location in a repository. This means we are changing the resource.

   There is more complication, but it would be nice to do it. If we run into unsolvable problems, then we can stop. But baseURI as a minimum. 

   Verification tooling would have to be updated as it not designed to handle this circumstance. If there is a need for this, then we can correct this in the verification tooling. 

   Does this resolve the Phase 1 #6 wish. "Support import into an existing empty container."

   We have been assuming that the container is going to be the same, host/port is a hard one to adjust for, changing base URI in Tomcat is somewhat easier. 

   Don’t want to get sidetracked on this issue and not achieve the sprint goals.

   Base Path is generally “/fcrepo/rest”

   Ingesting in to a Hydra instance under /dev and then after verifying moving it to /prod.

   Esmé Cowles will make a ticket or two and point to pull/48 as a first stab and move onto integration tests.

   Final question “What would we want inter-resource relationships to look like.” when ingesting to a new location. Principle was what would it look like if you exported the entire repository and import the entire repository. We haven’t talk through all the possibilities, it would be good to make sure we agree on this.

    

2. Validation

   https://github.com/fcrepo4-labs/fcrepo-import-export-verify/pull/7

   Hope the PR is complete, Josh has not tested but feels it is almost there. The latest commit just changed the default logger level.

   Should be able to test the latest version this afternoon and merge.

   It would be great if that issue could be closed, and the config file as changed a bit and that needs to be dealt with.

   Won’t have working tool until the update to deal with new config file options. Should be a quick fix (possibly completed today).

   Still haven’t sorted out the issues around verifying RDF, filtering out server managed triples.

   Can Nick help with verifying PRs or with updating the code to test the config, Nick will take

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2332

   .

   If you exported and then tried to verify against a Fedora instance that might have new objects you will not get any errors. The system is not designed to check both ways.

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2322

   .

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2307

   is around verifying a Fedora to another Fedora too.

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2329

   this is trying to check something, it finds an error and breaks off. What we want is for it to deal with the error and move on. 

   Next person that runs in the “Too many open files in system” should document the steps in a new JIRA ticket.

   Nick has done lubm and the 10k indirects and never run into this. Josh ran the one-click on his machine and he may have had other applications which could have used up some file handles.

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2329

   generally the error returned from Fedora is a 404 not a “Too many open files in system”. Remove that error from the ticket so as not to confuse the issue.

   Josh will test PR-7 and that will close

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2284

   .

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2190

   &

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2309

   is done once Nick completes

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2332

   .

   Josh will next take

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2303

   .

   Probably need to walk through all the verification tickets and close tickets that might have been resolved by existing work.

   Jira
   server DuraSpace JIRA columns summary,type,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13801 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

    

3. Logging

   https://github.com/fcrepo4-labs/fcrepo-import-export/pull/49

   There is different logging on the application side,

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2169

   and

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2170

   is about a different kind of log which is more of an audit log.

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2237

   is a different issue but has some discussion around the log format in the notes.

    

4. Esmé Cowles is creating a ticket for setting Digest header when importing checksum for binary

    

5. Danny Bernstein is moving onto

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2296

   .

6. Andrew Woods suggests we all add more words in IRC Standup notes so people can understand where everyone is at.

[Import/Export Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {and/or brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {and/or brief textual description}
Blockers:
  {brief textual description}