You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Date:

Attendees: Simeon, Steven, Lynette, Huda, Greg

Regrets: Jason, Tim

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 
    • 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 DFA approval (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
      • User reps D&A meeting: Need to re-follow up
        • Good to have knowledge panel lite mockups or examples ready to show
        • Also need to show entity page examples

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.
  • 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.

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? 
  • Miro board (diagramming): https://miro.com/app/board/o9J_lfXUUj8=/ 
  • Notes space: https://docs.google.com/document/d/1TVPBFak7DkfjBptKl-pCMWQnOaiWHB0XCHswiB3Fr9g/edit?usp=sharing
  • 2021-02-05 discussion
    • Purpose? Vision for mid-term (3-5 years) transition to support linked-data at Cornell. May include things we don't yet have or cannot yet do, but not long-term vision of post-MARC environment
    • Important to understand sources of truth (primary data) and where there is derivative data
    • Imagine landscape with items described in multiple formats including at least MARC, BF, DC (eCommons), JSTOR
    • Imagine all items indexed and discoverable via D&A
    • Functions of "Aggregated index, allowing pivoting & ETL"
      • Includes current functionality of Frances' indexing
      • Does it include any editing?
      • Is there interaction with CULAR?
      • Includes indexing associated with DCP
    • What interfaces or functionality do we expect for the connecting lines?
    • Do we need a diagram for now (or at least July 1, 2021 with Voyager gone)?
  • 2021-03-05 Jason plans to update diagram and create narrative around it, hope to discuss next week

Other Topics

  • PCC/Sinopia and SVDE shape analysis
    • 2021-03-19 Steven has been working through a spreadsheet of 400+ lines to compare the shape of SVDE data with the PCC/Sinopia profile. He is finding that there are many many differences which will severely limit how well Sinopia will be able to consume and edit SVDE data. For the purposes of QA/Sinopia cloning, Steven could come up with some ldpaths but not sure whether the amount of data will be useful. Steven expects to be able to share the spreadsheet at the next Sinopia/SVDE meeting. Going forward we need to consider the role of versioning/documenting shape changes and validation at both scale and single descriptions. Justin's validation scripts: https://github.com/LD4P/dctap. Tom Baker's csv2shex: https://github.com/tombaker/csv2shex
  • OCLC Linked Data / Entities Advisory Group
    • 2021-03-05 See comments above
  • PCC - Sinopia collaboration
    • 2021-02-05 Charge to form a new group for documentation, mentoring etc is under reviews
  • PCC Task Group on Non-RDA Entities
    • 2021-01-15 PCC reviewed proposal but no decisions made yet, looking at description wrt cataloger use, discussion will continue
  • Default branch name - Working through repositories in Renaming of LD4P Repositories
    • Created Renaming of LD4P Repositories page to identify Cornell repos, provide instructions, and track progress.
    • ACTION - Huda Khan to look at changing to `main` for LD4P/discovery (and update the Blacklight Cornell fork for LD4P3 to bring in the latest)
    • 3/19: Update: DONE with respect to discovery.  Need to wait on Blacklight upstream for LD4P3 fork
  • SVDE Workshop - several attended
    • Impressed by clear presentation of models and active APIs (REST and GraphQL)
    • Expecting models to be fully implemented this summer
    • At some time might want to add module to QA to query against GraphQL
  • Authorities in FOLIO
    • Hope to include URIs as part of Cornell FOLIO migration, possible LD4P work

Upcoming meetings

  • https://kula.uvic.ca/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"
  • code4lib - Expecting to attend: Huda, Steven, Lynette, Greg
    • Steven will be presenting poster on Discogs work
  • Lynette doing a QA presentation at Samvera partner call in June

Next Meeting(s), anyone out?:

  • 2021-03-19 Tim (vaccination #2)
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.