Versions Compared

Old Version 2

changes.mady.by.user E. Lynette Rayle

Saved on

compared with

New Version Current

changes.mady.by.user Simeon Warner

Saved on

Key

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

...

Attendees: Lynette, Huda, Tim, Greg, Simeon, Steven (late), Jason

Regrets: 

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
  • Research: how to go from knowledge graph to an index
  • DASH! (Displaying Authorities Seamlessly Here)
    • Dashboard design meeting kickoff notes
    • https://docs.google.com/document/d/1PgQi3xobsPhr9DUHU_YGeimL1OjNiiTdkiNWb36r3Gg/edit
    • Usability testing and followup for DASH: Usability results
    • 2021-12-0310
      • Lenora: User reps are fine as-is (no concerns) but had not yet heard back from a few more people in her unit. By end of the week (today) would hear if any concerns exist. On Monday, Tim will email and point out that it would be easier to do while Tim is still here; won't be here for next D&A Spring in mid-JanuaryTracey had feedback on a particular Paramount Records box set that looks bizarre in catalog (pulling in too much information and might be some incorrect information being pulled in - ToC 's and other feedback focused on three comments: 1 will be fix on Monday is something noticed in current system with "back to list" not making sense if user came from different context; case of work by multiple authors has only one in 100 field, other in 700 – the author in the 100 gets prime spot in item page where second author is relegated to other contributors which doesn't currently get an info button (and should any other contributors in 700 get info button?); reps like the subject detail page and exploring options for navigating subject data and getting to subject detail page. Additional exploration required for both of these cases.
      • Hope to work on DASH! video next week is long but additional field is a very long, unformatted list of everything in the collection); she emailed a Tim and Huda, referencing that the cataloger already put in a link to Discogs. https://perma.cc/4URM-2MCP (Perma used since this page'll be updated shortly)
  • BANG! (Bibliographic Aspects Newly GUI'd)
    • Jamboard link
    • Expect to include Works. Need to do something beyond what we already have live from the OCLC concordance data.
    • 2021-11-12:
    • Huda revisiting item view integration, included "online" field info and indicate (for debugging) whether related works coming in from PCC ISBN or LCCN relationships, etc. Began work on LOC Hubs in this page, some debugging, and thinking about how to bring this information back so it connects to catalog results.  Also need to revisit work to work relationships (have a data file and will bring this in for viewing later). 
      • Steven researching IMDB and Dune : )
    • Though we don't have the movie in our collection yet, Dune (2021) it's a pretty good example for BANG because it's based on a book, but unfortunately for us IMDB's mission isn't to plug books in their RDF (no schema:isBasedOn assertions). I think we might still want to consider whether to incorporate schema:image, schema:trailer (embed or link out), schema:description (though in some cases we might have summary notes for movies in our bibs already).
    • Ratings and reviews are interesting to consider... I doubt some librarians would be open to opinions being added to our descriptions, but I remember reading a little while back that the Vet Library was actively collecting for pleasure movies, etc. for students to help with supporting belonging, stress, campus life. As someone trying to view a movie from that perspective ratings, reviews, and trailers are helpful.
      • It's not in the schema block, but we might be able to recreate the more like this part of the IMDB page. Which is a little more work-to-work BANG-like.
    • There is really great data in Wikidata and IMDB, but not finding a shared identifier for each example in our catalog. If we think this is worth pursuing (we should confirm if browsing/pleasure viewing is a use case), we might have to rely on "fuzzy" matching, similar to the Discogs work when there is no id
    • 2021-12-03:
      • Steven waiting on SHARE-VDE queries; will work with Huda on them. Huda had run queries to get work-to-work relationships; if Steven's query does not time out, great. Will need to iterate on the queries anyhow given the type assertions. Wondering whether this will yield same use cases available in MARC. Huda's query was limited to Works that had Instances
      • Huda worked on LoC Hub data integration; if you're on an item page, looks up instance from LoC, finds Work, finds Hub and then finds related Translations and then related works, their Instances and then ISBNS and LCCNS where available  for those instances. Need to next hook up to SOLR look-up. Still some oddities of SOLR look-ups (e.g.: geography returns for Hamlet); will be on lookout for strange data matches
      • LoC Hub data should be downloadable next year... for the moment, relying on multiple AJAX requests
    • 2021-12-10
      • ISBNs and LCCNs returned from LOC Hubs navigation (focusing for translation hubs at the moment) now tied to Solr lookups and returning results in page
      • Worked on seeing if I could set up a proxy controller to get IMDB page and retrieve the JSON-LD with the Schema.org markup (and it seems to work!)
      • Also reviewed some articles around discovery/visual representations based on FRBR/BIBFRAME, etc.: (Google doc). Objective: Identify possible use cases for discovery using work-instance relationships as well as look at examples of interface design for representing this information
        • Perhaps easier to demonstrate usefulness of BIBFRAME/semantic model for more complex use cases (although article focused on visualizations and found visualizations were effective regardless of complexity when compared with a faceted results view)
      • To dos: Still need to use the work to work relationships data (which is based on a partial query run) (i.e. related, etc.) and bring that to the page.  Will try to get that done by end of year. 
        • Using Wikidata relationships between item and IMDB to get appropriate IMDB link 
        • Design work/review options for displaying information to users (works/instances and how/whether to modify the current catalog view focus on item)
  • DAG Calls
    • 2021-12-03 - next Tuesday, last call of 2021! Recap slides to be made, and hope for some discussion on people's thoughts regarding topics and ideas for next year

...

  • Github branch renaming
    • See Renaming of LD4P Repositories – cul/blacklight-cornell now uses main but still has the old master branch too
    • Expect to be able switch this in LD4P as part of D&A work
  • Sinolio - Sinopia-FOLIO
    • 2021-12-03: Jeremy gave Jason access to a test instance of FOLIO on the Stanford servers. No data in there... but can log in10 - There is a now an "Export to Catalog" button in Sinopia that shows for Jason as a result of knowing that Jason is part of Cornell. Doesn't yet do anything
  • OCLC Linked Data / Entities Advisory Group
    • 2021-11-19 Moved away from Wikibase, could mean they reuse properties (at least rdf:type, rdfs:label, etc.) There will be a subscription for accessing the editor, and APIs. Not part of the cataloger subscription, but expect news soon(?) about going live and pricing models. LOD will be published/dereferenceable . Asked how they would justify the extra cost... they believe there’s a value for libraries to contribute data so that it’s shared. There's another round of testing.12-10 OCLC presented at bigheads meeting this week, in testing
  • ISNI - made a soft launch of LOD this week. Shhh... they are providing data dumps now, dereferenceable LOD sometime in 2022. https://isni.org/page/linked-data/
  • PCC 
    • 2021-10-27 Definitions and non-RDA examples in MARC examples continued to shift, but should be able to finalize the spreadsheet that generates the RDF today.
    • 2021-1112-19 - 10 Nothing new to report.
  • Authorities in FOLIO
    • 2021-11-19 Julia walked group through what deletes would take in the current plan, it would be challenging to do this using a combination of Blacklight, Connexion, and FOLIO. Jenn and Nick suggested thinking about FOLIO authorities app (to keep us in FOLIO for search, copying, and editing in BIBs), timeline for EBSCO work on authorities app is ingest/search in Lotus (April)
    • 2021-12-10
      • Frances working to parse data and then Nick will use data via API to generate report. Expect the need to iterate.
      • Jenn did some analysis on copy of old Voyager data to look which controlled identifiers might be pull into BIBs

Upcoming meetings

Next Meeting(s), anyone out?:

  • 2021-12-10 17 - no (Tim, Huda, Greg); Jason late (candidate presentation); Steven late or missing (candidate)