Page History

...

• 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 
  • Production requirements and functionality – Production decision points
  • Discogs data use - in production since January 2021
    • ACTION (during March D&A sprint): Tim Worrall will raise usability testing for D&A queue (don't carry forward in notes as now outside of LD4P)
      • 3/12: Will be raised in sprint next week
•  Strand 2: research: how to go from knowledge graph to an index
  • Research decision points, Use cases 
  • 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
    • 2021-02-19 Tim has been working on entity page. Notes a number of issues with the Historopedia timeline such as items with same date being hidden, but performance is good
      • 2021-03-05 Tim resolved a number of issues. Next week will return to work on this and deal with influence-for and influenced-by presentation
      • 2021-03-19 Tim still working on this
  • 2021-03-12: Considering KPAOW zero (streamlined knowledge panels). Have begun discussing what should go in a streamlined version.
    • ACTION - Huda Khan to line up meeting with D&A user reps
      • DONE: Scheduled for April 9th, 9-10 (Moved the LD4P3 meeting to this time)
  • Planning for discovery work - Next steps
    • Usability testing for DASH
      • Confirm gift card process with financial office
        • 3/19: Financial office waiting for their own IRB process (as they noted earlier).  Can still send out recruitment emails soon
      • Recruitment emails to be sent out next week
        • 2021-03-19 Planning to use Tobi and Wendy's contacts and email forwarding
      • Should be able to tie up any development on author/subject by end of March, so considering first two weeks of April for scheduling tests
        • 2021-03-19 On target
      • Need to finalize usability tasks for both authors and subjects
    • User reps D&A meeting: Need to re-follow up
      • Good to have knowledge panel lite mockups or examples ready to show
        • Started some mockup brainstorming here: https://jamboard.google.com/d/1PXLAu0XTzaQhe9vw6OcAdsqJItFJ4U-FStgm9lA1CHc/viewer?f=0 
      • Also need to show entity page examples
    • SVDE Works
      • 2021-03-19 Steven has looked at SVDE works and is thinking about how to find works via ISBN to then find other Instances. Is looking via SPARQL on Dave's ingested data
    • eResources
      • Discussion with small group regarding call number classifications on e-resources, where there is/isn't sufficient metadata compared to equivalent/related physical objects.  Possibility of gathering some useful examples around needs/wishes around e-resource discovery. 

Linked-Data Authority Support (WP2)

• Qa Sinopia Collaboration – Support and evolve QA+cache instance for use with QA
  
  • 2021-03-19:
    • No meetings this week for QA/Sinopia this week.
    • See Steven's comments on ShareVDE data.  Dave wants to look at making a direct connection to ShareVDE GraphQL API and translate it on-the-fly to something that QA can work with.  There are going to be some complexities with how to structure queries and extended context based on the variability of data shapes.
• Search API Best Practices for Authoritative Data working group
  • 2021-03-19:
    • Created the charter for the next working group describing the expected outputs for change management.  I plan to announce the charter on Monday and begin reaching out to individuals to get folks on board.
• Cache Containerization Plan - Develop a sustainable solution that others can deploy
  
  2021-02-19 Greg completed CloudFormation template that allows someone to spin up a QA service in AWS easily. About 500 lines of template code that brings this very close to being a turnkey solution (in services-ci branch).Greg notes pre-reqs for spinning this up: S3 bucket for configs etc. which could be added to another template.
  • When complete Lynette will test, then ask Dave to test, then ask Stanford folks. Greg will also create a demo screencast.
  • What about replacing the current QA setup with this new approach? Would need to check authority configuration and correct setup for load. Lynette notes need to copy over the DB to retain history
  Next steps
  • start to look at containerize Dave's setup. Two steps: 1) code to serve from cache, 2) indexing process
  • think about instructions for a vanilla linux server setup
  2021-02-26
  • Cache containerization discussion in QA-Sinopia meeting: We mostly talked about the next steps for the cache creating two containers: 1) container for API requests to retrieve cached data, 2) container to ingest data downloads and creation of the Lucene index.  This is fairly straight forward in the current approach of a full-data dump and ingest.  It is expected that there will be some complexities to resolve in how to update indices when change management techniques are deployed by authority providers that allow for incremental updates.  We punted that discussion until later when the format of change management streams is defined.  Stanford was asked their preferred deploy platform and they indicated that AWS was preferred.  
  • Greg will work with Dave when he starts work on containers and tester and sounding board
  • CloudFormation - Greg has written templates and Lynette is going to test these out (will document time taken). Hope to find anything missing in template or documentation, perhaps some permissions issues will be revealed too that will allow documentation of critical permissions
  • Next Greg will look at prerequisites that need to be set up and work to template these in a helper template
  • 2021-03-05
    • Completed prerequisites template which includes S3 bucket and EFS filesystem - next step is to document instructions and how then to move to next template
    • Greg/Lynette to coordinate Lynette's testing next week - use feedback to refine documentation
    • Then create demo screencast
  • 2021-03-16
    • Working on writing documentation
    • Need to discuss approach with Dave Eichmann.  Good to test run the containerization process.  Greg and/or Lynette will follow up with Dave.
    • Lynette can try out the lookup container next week
  • 2021-03-19
    • Lynette began documenting the deployment to AWS adding in an overview, background knowledge, and architecture sections.  Next is to start looking at how to use the templates.
    • Greg is going to follow up with Dave about how to work with him on his containerization efforts
    • Expect to work on demo screencast after refining documentation

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

...