...
- Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
- 2021-01-22
- No meeting with Stanford. Met with Steven and Dave to review the Evaluation of New Indexing Approach project board. We moved 6 issues into the Under Exploration column. 5 appear to be related to indexing. 2 need review of the tests to determine if they would be expected to pass. 1 required exploration in QA. For the QA one, the issue was there was an actual line break in the triple which is not supported. So the question is why Jena produced a triple with a line break. Is the problem in the source data or should Dave's code change any line break to the proper escape sequence (i.e. `\n`). The plan is to meet for 30 min once a week either before or after the meeting with Stanford to review the board and work our way through the issues so the new indexing scheme can become production
- 2021-01-29: no Stanford meeting. Still 5 issues; one for GeoNames that does not pass test though target URI is there. Remaining 4 are in Dave's court. Steven checking whether any other authorities have line breaks; Dave considering generalized approach to repair the line break in the triples. Exploring whether problem in Jena Fuseki or if it is an artifact of making this a blob in the indexing process.
- 2021-01-22
- Cache Containerization Plan - Develop a sustainable solution that others can deploy
- 2021-01-22
- Greg has started a new branch for container in ECS. So far ECS will run task, need to work on load balancer config and deal with restart on error/quit. Require ECS service for this
- Started AWS documentation - in aws templates folder README, need to describe environment file and steps to implement
- 2021-01-29: lots of documentation and templating work; one critical piece needing completion (getting service that takes all pieces together and keeps container running in service into a template). rest is good. nearing point where we can put in front of others and say 'give it a spin'. Likely finishing up the template of last critical service piece for next week
- 2021-01-22
- Search API Best Practices for Authoritative Data working group
- 2021-01-22
- The group is reviewing the Supporting cataloger inclusion of external authoritative data document. We will meet on Monday Jan 25 for the final meeting of the first charter. We will also explore topics for the next charter. Potential topics: language processing, change management, moving user stories to practical and specific recommendations, and triple stores and other technologies. The next charter will likely start in March to give folks some time off between and me to prepare for the selected topic.
- 2021-01-29: met and did informal voting in group for next topics; also has survey (posted in Slack) that has descriptions of each area, potential areas and video discussion in meeting to ensure sense of the potential topics. Will then send to broader group to get sense of what broader community wants as next steps. 4 areas:
- 1. change management (source data to consumers), 2nd (tie) among group
- 2. language processing (anything to do with language),
- 3. moving forward from what has been done (user stories to specific recommendations),-- 1st among group
- 4. Linked data specific approaches and what implications does it have for our data being in LD, what are the tools and what can be leveraged (producer side)? 2nd (tie) among group
- 1. change management (source data to consumers), 2nd (tie) among group
- 2021-01-29: plus delta done. plus saying everything well organized and a delta saying that everything was really well organized. steering of conversation based on what was brought to meeting ahead of time. Concerns expressed around whether time will be allocated to adopt recommendations
- 2021-01-29: work done on supporting cataloging inclusion (categorized version of user stories); meeting one more time next Monday to work through rest.
- 2021-01-29: got to a good place with good output!
- 2021-01-22
...