Page History

...

Jason Kovarito ask Tracey if she has the capacity to discuss librarian instruction at CUL re. possible use cases. Question had come up in the context of the dashboard use case "Instructional librarians want to teach users how to navigate library materials using subject headings. Combined with Classification/LCSH taxonomy mapping"

Huda Khan

and

Tim Worrall

work to continue to explore the dashboard design and requirements

2020-09-25 in progress, will discuss with Astrid & Tim next week
2020-10-02: Kickoff design meeting happened → Huda Khan Tim Worrall& astrid will look at different aspects more and regroup in 2 weeks (Meeting set for 10/14)
10/14 meeting and linked initial ideas
2020-10-16 Next steps: understand data better, discuss with Steve, refine design ideas, think about facilities for user and then work toward a prototype2020-10-23 Tracey is happy to help but wait until November

Greg Delisleto explore how to get the container version that Lynette has on her laptop up on AWS. Question about how to handle environment variables outside of the checked in docker container so that users can config
- 2020-10-09 On laptop Lynette had an entrypoint script which worked fine to allocate assets and connect to mysql etc., this doesn't work on AWS. Lynette is trying to move these processes into the Docker file. Works for bundling but not for precompile, has some input from Justin, Greg will look into the DB connection. Some concern that we are having to make many changes for AWS, will the new version work on laptop or other VM? (changes so far do work on laptop too)
- 2020-10-16 23 Greg has had limited time this week, Lynette still trying to resolve problems with MySQL startup, having problems precompiling assets
Toward a demo and discussion with D&A:
- Huda Khan & Tim Worrall - Make sure the live demo meets the Discogs API terms of service in terms of linking and ack. – Had discussion with Melissa about how/where we show acks and licensing in general for our Blacklight. Could then link to this from all pages and perhaps a specific link to the details on this page. A bit more to do
  - 2020-10-09 - Code changes DONE, Tim thinking about whether we should remove not about wikidata which isn't part of the current production plan. Example: ld4p3-web.library.cornell.edu/catalog/6055667
- Huda Khan to discuss with Adam having a meeting with User Reps sometime after Oct 5
  - October 16th potential date/time: 3:30pm → need to send list of names to add to this meeting to Meredith - names added
- Tim Worrall to look into how we might display some language pointing out what data is not used in search. For example, what if a user sees the record label in Discogs data and then tries searching on that (which they can't)? Per Tracey suggestionPartly contingent upon the presentation approach selected. Think about it more after 2020-10-16 meetingpulled Lynette's branch and had a quick look, will have more time next week. Lynette comments that the precompile is the key problem

Agenda

Discovery (WP3)

https://github.com/LD4P/discovery/projects/2 for issues etc.
Preliminary draft of a discovery plan- intended to get feedback: https://docs.google.com/document/d/1zKYW7FQVVNvyd0XjjW0qWznX9PC3jbmOE6Kz_yygPjs/edit?usp=sharing
Strand 1: production piece (i.e.: picking features we've already worked on to then push those into production): discogs, autosuggest. Feature branches in the code to work on features in isolation. Still need to discuss discogs with Tracey (post- 9/2). Preliminary pass with discogs features using latest production (from a few days ago) successful (tried on dev vm and will try on ld4p3 demo using continuous integration later)
- 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
  - Following up after user reps meeting
    - ACTION - Tim will sort out code in LD4P3 repo and look at adding button to highlight Discogs field next week
    - Steven notes possibility of generalizing the highlight button functionality to other external data, not currently in scope. Book covers come in dynamically through ISBN. ToC is being looked at for addition to index (so slightly different)
    - Tim hopes to demo to the User Reps on the Nov 5 meeting
    See actions above from last week
    - Have branch with discogs code on dev VM and demo server from LD4P fork, but still issues with the assets folder under Rails not showing current version (these are generally copied in during the Rails deploy process)
    - Update 10/9/2020: Manually cleared out the assets folder on the two rails servers and ran Jenkins deploy more than once and saw only one copy of the files, so hopefully this is fine now. Will keep an eye on the assets folders.
    - How do we run the demo meeting next week? Simeon intro mention demo and mockups of alternatives, turn over to Steven to mention catalog override and then demo from Tim
Strand 2: research: how to go from knowledge graph to an index - what decisions are needed. What are the data sources for each (e.g.: how many Cornell faculty in wikidata)? Present: reviewing data sources and questions. Should have more worked out in a week or two. Main areas of concern: browsing and dashboard... and anything we can do to help patrons navigate our collections and how we can highlight an entity... and what does that mean for the index? How do we capture the relevant bits of the graph for an index? Is there a repo for this? Not yet... but can use discovery repo (https://github.com/ld4p/discovery) we already have to capture any queries or related work.
- Research decision points
- Use cases - first review 2020-09-18
  - Interest in the dashboard idea (full page for entity) that extends on the idea of an embedded knowledge panel
  - Goal of functional prototype for end of year
  - How will we test it? Remote testing would work but will students want/have-time to talk with us? Can we pay them?
- Discovery Affinity Group is looking at design ideas
- 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-10-23 Demo! Huda will continue to work on design elements for the dashboard, wondering about additional data connections, get to a sufficiently good prototype to start to get some feedback. Next Tuesday there will be a discussion in DAG of data connections to support particular user tasks
  - Steven notes Matt Miller work on connections between library authority work and wikidata, also PCC has wikidata pilot project which has some people creating wikidata entities and linking to them from MARC. Most work in special collections so generalization not always immediate

Linked-Data Authority Support (WP2) - A key element of this work package is a sustainable solution that others can deploy. Questions of budget for deployment. Need to get all code into LD4P repository. What would a good end-product look like both for our maintenance and for others to use

Qa Sinopia Collaboration
- 2020-10-16Validation testing of 23 - Dave's new approach to indexing. Now in Dave's camp
  - 2020-10-16 Validation testing - first take on the reindexing
  - 2020-10-23 Validation testing - improvements on first take. New data on integration server (lookup-int.ld4l.org), Steven will help Dave understand this problem cases
- 2020-10-23 Ongoing discussion with Sinopia team and SVDE folks about integrations. We are not yet clear about whether SVDE will provide a direct search API or appropriate incremental mechanisms for using Dave's cache
Cache Containerization Plan
- 2020-10-16 -Still an issue with getting MySQL to start on AWS23 - See notes above.

Search API Best Practices for Authoritative Data working group

2020-10-1623

Next meeting - 2020-10-26

ACTION: Lynette needs to put together survey for cataloger user stories for PCC feedback and ranking by working group.

Started. Requested feedback on prioritization wording, but received no comments.

Code Block

EXAMPLE:
As a cataloger, I want to … a user story will go here…
 * REQUIRED - The system is unusable without the feature represented in the user story
 * HIGH USE - The feature represented by the user story would be used a lot.
 * NICE TO HAVE - The feature represented by the user story would be helpful, but the system is useful without it.
 * DON’T NEED - I do not expect to use the feature represented by the user story.

Suggestions:
- Change from ranking to sorting. Might be problematic with the number of user stories (> 20).
- Going to look into a combination approach where there are 5 bins sorting from High to Low and each bin has a limit on the number of allowed user stories.

From 2020-01-19 Sinopia call
- Note many issues hidden in https://github.com/LD4P/sinopia_editor/issues/2166 → ACTION: Steven will reconcile the list with existing issues and work out what isn't being looked at

Developing Cornell's functional requirements in order to move toward linked data

- C.f. Stanford functional requirements document: https://docs.google.com/document/d/18H6zYGwKuCg3SZqm9Q_cxkZThcdmBjknE6HdtQ-RRzk/edit#heading=h.4fu64x8jzm6e
- What does success look like? And then how do we get there?
- 2020-09-25 Jason drafted an introduction for LTS staff and no capacity right now in LTS, perhaps discuss again next week as to what next steps will be. Jason and Steven will discuss this week
- 2020-10-02 Jason will collect information to prime brainstorming from LTS, think about brainstorming then discussions

Page tree

Versions Compared

Old Version 1

New Version Current

Key

Agenda