Versions Compared

Old Version 2

changes.mady.by.user Steven Folsom

Saved on

compared with

New Version 3

changes.mady.by.user E. Lynette Rayle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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-23 Greg has pulled Lynette's branch and had a quick look, will have more time next week. Lynette comments that the precompile is the key problem
    • 2020-10-30 QA Server container deployment now works (hurrah!). Some cleanup to do in the repo then now need to turn this into a real ci/cd circle. When cleanup and testing done then think about how to switch over lookup.ld4l.org instance to AWS container version
  • Steven Folsom ACTION: Steven will reconcile the list with existing issues and work out what isn't being looked at https://github.com/LD4P/sinopia_editor/issues/2166 - DONE. Most concerns are being address by one or more issues in the QA and/or Sinopia efforts. Some issues lack enough information to know how or if we're already acting to improve on the experience.

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
          • 2020-10-30 Tim has been working on this
        • 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
  • 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
        • Discovery Affinity Group meeting:  Provided recap of Wikidata and LC connections we've already included.  Started on discussion of BIBFRAME specifics.  Wil
      • 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

...

  • Qa Sinopia Collaboration
    • 2020-10-23  - Dave's new approach to indexing2020-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 cache30 Didn't meet this week.  Lynette at conference.
  • Cache Containerization Plan
    • 2020-10-23 30 - See notes above.
  • Search API Best Practices for Authoritative Data working group 
    • 2020-10-2330
      • Next meeting Meeting - 2020-10-26 - Completed developer user stories.  Showed a preview of the survey to send to the group and PCC to prioritize the cataloger user stories.  The UI for the sorting into bins is bad.  The bins don't stay on the screen as you scroll up and down to view all the user stories.  This will make moving stories into bins difficult.  I'm exploring CSS that might make this better.  Next meeting will start on Provider user stories.
      • ACTION: Lynette needs to finalize the survey for cataloger user stories for PCC feedback and ranking by working group. 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

...