...
- Jason Kovari will continue functional requirements efforts, starting with workflow diagramming
- Organizing cohort effort around this is on-hold until January; Jason has not yet made progress beyond: https://miro.com/app/board/o9J_lfXUUj8=/ ; will pick up work either before Break or immediately following
- 2020-12-18 January is a most auspicious time for the consideration of functional requirements
- E. Lynette Rayle to finalize the survey for cataloger user stories for PCC feedback and ranking by working group, check with IRB
- 2020-12-11 results now with 61 respondents
- Top 5: context, filtering by class, broader and narrower, knowing an entity doesn't exist, edit plus adding URI
- Discussion in meeting of the "knowing an entity doesn't exist" use case - sense that catalogers understand the problem of not being sure where something has been found or not, they broaden search to get a list and then carefully read through it. Perhaps a key thing here is relevancy
- Sense is that with 61 responses we have useful information to move ahead with. Will close survey midday today
- ACTION - Lynette will write this up and present to working group on Monday
- 2020-12-18 The simple summary of results are in review by the team with the intention to send it out to the broader community. A more detailed summary of the working group output including all levels of user stories is being developed in document Supporting cataloger inclusion of external authoritative data - COMMENTS WELCOME
- Expect to finish up document in early January then consider possible new charter for the group
- 2020-12-11 results now with 61 respondents
Agenda
Discovery (WP3)
- https://github.com/LD4P/discovery/projects/2 for issues etc.
- Draft of a discovery plan: https://docs.google.com/document/d/1zKYW7FQVVNvyd0XjjW0qWznX9PC3jbmOE6Kz_yygPjs/edit?usp=sharing
- Strand 1: production piece
- Steps:
- Discussion with Tracey re. use case and benefit – DONE
- LTS engagement re. metadata - DONE
- Production requirements and functionality – Production decision points
- Demo and discussion with D&A User Reps and dev team – DONE
- Implementation work
- 2020-12-11 Discogs is now in the official schedule for January D&A sprint
- Steps:
- Strand 2: research: how to go from knowledge graph to an index
- Research decision points
- Use cases - first review 2020-09-18
- First goal: DASH! dashboard (full page for entity) that extends on the idea of an embedded knowledge panel, aim to have functional prototype for end of year
- DASH! (Displaying Authorities Seamlessly Here)
- Dashboard design meeting kickoff notes - will also try to understand what our data will support or connections to other data sources
- https://docs.google.com/document/d/1PgQi3xobsPhr9DUHU_YGeimL1OjNiiTdkiNWb36r3Gg/edit2020-12-04
- Period-O info and with subject heading components/subfields - some of which have URIs and some are cannot be mapped. For temporal subfields that are not years (e.g.: 20th century), will/may hard code. Some subject subheadings that are Geographic do not have URIs; for a subject without temporal information but with narrower terms with temporal information, working to put those on the timeline
- Can solve the multiple AJAX requests by building an index that mitigates the extent of calls; worry that may become super-large index but not a concern at the moment. wants to put as much work on client side but slow that way... plus there could be useful information to search. leaning toward more index-heavy for information we require Next step: decide how much more should go into index; moving around information on page to raise catalog results and also allowing for a "see more" button
- 2020-12-11
- Moved information into the index for broader/narrower URIs, as well as wikidata URI. This helped clean up the code/which pieces were waiting for information, and now the broader/narrower components will show up on the timeline. If the subject being displayed has no temporal info of its own, the timeline is shifted to focus on one of the broader/narrower subjects.
- Calls to the production subject browse (for now) and the LD4P2 subject index that included call number facets allow for display of "works about" with number and a link to the call number browse.
- The map and timeline have been moved to the same section, with a single panel on the right. Design discussions around how to perhaps improve that/collapse, etc.
- Had a quick chat with Tim and Astrid yesterday: Notes, Astrid's design ideas
- In progress: Learning about how to query eCommons. Reached out to various D&A folks and have references to review. Need either simple keyword search or subject field search. Looking like probably DSpace API
- eCommons may be co-indexed with DCP for bento box - not sure?
- eCommons would be nice to add if quick/easy but not worth sinking large amounts of time into at this stage
- Next steps:
- Highlighting the map based on which timeline article has been selected
- Moving over the search results
- Tim will start looking at Agent/Authors page for dashboard when ESMIS sprint finished
- Some work to move indexes between VMs, in order to vacate/shutdown LD4P2 machine and have everything on LD4P3 cluster
- Discussion
- Steven notes past D&A discussions where there was interest in having access to bento results when one is in the catalog, the tabbed interface that Astrid mocked up is an interesting way to approach this
- Updated the UI to be closer to the design from the mockup, although more work to be done
- Top-level box for main information with horizontal layout of broader/narrower. Leaving out similar for the time being or will put in a separate box to keep the broader/narrower relationships clearer.
- Created tabs to bring in library catalog results, digital collections, and eCommons. Running into some errors with the latter but technically the URL for the Solr collection (which is hosted on the same Solr as digital collections but not integrated with digital collection results) is correct.
- Considered reusing the Bento Box results, but would need to extend the Bento Box configuration (perhaps?) or pass additional parameters to support subject field search (since we're targeting subject fields and not just regular keyword searches).
- Library catalog and digital collection results using the JSON format from the Blacklight results. Repositories relying on direct Solr request
- Need to also pick and implement a consistent styling across tabs
- Need to update display/code to handle when sections not present (so as not to just show empty boxes/weird layout)
- Wondering if
- Tim started work on the agent/author side, some open questions where they are different enough to consider some different layout items (e.g. works by and works about)
Linked-Data Authority Support (WP2)
- Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
- 2020-12-04 Working on creating issues for all remaining work on new indexing approach. Started in Uber issue (Issue #383). Addressed 2 issues in QA
- 2020-12-04 Dave's indexing accuracy for tests: Dave thinks it is better across the board; Lynette building comparison into UI, currently manual process. Some conversations around this are happening in Slack – moving that documentation into Issues to allow for post-fact review. Performance is consistently better – issues is ensuring that accuracy is consistently better... and assessing why if not. Analysis up to this point was primarily for LoC... now doing analysis for all authorities. Users tend to ask more of QA than they ask of other tools that already exist (e.g.: when search id.loc or OCLC, there is a lot of paging.. but in user requests for QA, expectation is that desired result is within first few). OCLC also has weight that accounts for frequency of use
- 18
- Stanford off this week but have a conversation with Dave in regard to containerization work. Dave continues to work through issues
- Steven went through the github board to look at everything that wasn't a data connection issue and provide advice where possible
- We note LC announcement of more frequent updates
- There is a known issue in Sinopia where a user creates an entity for a URI but bad RDF is created – discussed with PCC and hopes to prioritize. Lynette notes that QA has a way to do a cache-bypass fetch for a particular URI
- Cache Containerization Plan - Develop a sustainable solution that others can deploy
- 2020-12-11 Ball is in Greg's court. Will release new version before the QA Sinopia meeting next Wednesday. Hope to have containerized DB up and running and push JSON config.18
- Work went well. DB containerized in same way as local config. MariaDB image loaded into container
- Working with Lynette, Greg set up some static volumes needed for use. Have found a way to use s3 buckets to manage data that users will have to update as authority files change
- Have JSON version of task definition for AWS. Adopters will have to edit this to configure a new deployment
- Have partial CloudFormation template to provision infrastructure if using AWS (Sinopia uses Terraform)
- Will continue this work, finish CloudFormation template and set up CI/CD environment. Then will need to share with community and get feedback (currently just set up on VPN) – have planned to have Stanford & Dave try replicating first
- 2020-12-11 Ball is in Greg's court. Will release new version before the QA Sinopia meeting next Wednesday. Hope to have containerized DB up and running and push JSON config.18
- Search API Best Practices for Authoritative Data working group
- 2020-12-11 See notes above. Next meeting on Monday, will categorize levels of user story today to show path from cataloger stories to provider stories. Technically this will be the last meeting of the WG. Will need to think about what is next in the New Year18 see above
Developing Cornell's functional requirements in order to move toward linked data
...
- OCLC Linked Data / Entities Advisory Group
- Lynette and Huda attended yesterday's meeting. Sticking with wikibase, expecting more UI work. More testing in January to extend from search (in last tests) to creating/viewing/editing entities
- PCC - Sinopia collaboration
- 2020-12-11 Discussion of what group(s) will take this forward18 Meeting today with a focus on profiles, hope to understand PCC work separate from Sinopia and also then connection with Sinopia implementation
- PCC Task Group on Non-RDA Entities
- 2020-11-20 The PCC non-RDA report was finalized and submitted to POCO earlier this week
- 2020-12-04: on PoCo agenda for 1/14; more after that
- Default branch name - WAIT until we can use github tools January 2021
- Samvera community meeting this month. Discogs & 024s. Steven led 024 conversation among music catalogers
- Steven gave update at CMS meeting this week, will follow up with Tracey, Beth and group in order to support flag that says "don't search discogs", else 024, else dynamic searchLynette is signed up to be a beta tester for github. Target for public release is end January
Upcoming meetings
- https://kula.journals.publicknowledgeproject.org/index.php/kula/announcement/view/1 . Call for Proposals - Special Issue: "The Metadata Issue: Metadata as Knowledge". Due January 31, 2021 (abstract 300-500 words). Includes "The use of linked open data to facilitate the interaction between metadata and bodies of knowledge" and "Cultural heritage organization (libraries, archives, galleries, and museums) and academic projects that contribute to or leverage open knowledge platforms such as Wikidata"
...