...
Attendees: Jason, Greg, Lynette, Huda, Steven, Simeon, Tim (from 9:30am)Regrets:
Actions from 2020-12-04 11 Cornell LD4P3 Meeting notes
- 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-11 Not ready to discuss yet. Not planning to organize cohort around workflows until January, Stanford is on break after today18 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-04 - Distributed with 19 participants in less than 24 hours. Will send another reminder today. Closing mid next week if there are weak responses. DONE
- Top three: seeing contextual info, filter by class-type, see broader/narrower Bottom three: updating local data if changed in original source; which field triggered a keyword match; if cannot find in local look-up don't want to go to original source and search there (need to dive further into these)2020-12-11 results now with 63 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 63 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
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/edit
- 2020-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
- 2020-12-18
- 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,
- Updated the UI to be closer to the design from the mockup, although more work to be done
Linked-Data Authority Support (WP2)
...