Page tree

Versions Compared

Key

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

...

  • 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
    • 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
    • Usability testing for DASH
      • 2021-04-16 - Usability testing is underway, will finish next week. Useful input on what users see/understand and what they struggle with. Users don't know what a repository is, can guess what digital collections means. Users tend to think that the author name link will get more information, don't see/understand info button – could mean adding tool tips and/or making button more obvious or even flip button/link or one link for info+search
      • 2021-04-23 - Five people helped with usability tests. Setting up final results document. High level:
        • Uncertainty of info button vs author link (or lack of understanding if same/separate). Tim has created issue in D&A
        • Good understanding of author page in general, opportunities for some clarification in labeling etc., influences tab well understood
        • On subject page the timeline scroll/zoom fast creating interaction problems, broader/narrower mixed understanding (difficult when subject is an event), "show all subject" checkbox not found easily, timeline/map connection was understood
      • 2021-04-30
        • Writing up usability test results
      • 2021-05-07
    • User reps D&A meeting: Expect next follow-up in August
      • Slides: from user reps meeting 2021-04-09 and result was "not no"
        • Positive feedback on linking back to catalog results
        • Questions about links and display from wikidata, other sources
        • End was to discuss more in August with possible discussion of how to move into production
        • User reps have slides and wanted demo link
        • Could have lite KP might to start, possible later entity pages – or perhaps both together
      • 2021-04-23 How much more work to do before August? Candidates:
        • Follow up on results from usability tests
        • Work on how smoothly the prototype works
        • Think about more consistent look between pages - Tim thinking of making some mockups of redesign
      • 2021-04-30
        • Working on a list of tasks for the final refinements stage. Includes aligning look & feel of the entity pages, Tim is looking into this. Current subject pages optimized for things with date ranges, what do we do for subjects without date ranges (e.g. microbiology)?
    • Video for DASH!, theme?
      • Sonic? Roadrunner?
  • BANG! (Bibliographic Aspects Newly GUI'd)
    • Expect to include Works. Need to do something beyond what we already have live from the OCLC concordance data.
    • Full OCLC concordance us 343M rows, and gzipped the file is 3.3GB
    • SVDE Works
      • 2021-02-26 Have to develop SPARQL queries to pull out certain sorts of connected Work. Don't expect data to be very dense but do expect that we would get useful connections between print and electronic for example. We already have a link based on the OCLC concordance file from several years ago.
      • ACTION - Steven Folsom and Huda Khan to work on building an equivalent of the OCLC concordance file based on SVDE data and then do a comparison to see how they are similar and different
        • 2021-04-02 Steven and Huda met to think about putting together queries to extract a similar dataset.  (Document for recording queries). Open questions about the counts – got 16k works from one view, got about 8k where limited to case with at least one instance. These numbers are much much lower than expected
        • 2021-04-16 Steven working with Dave on how to pull our SVDE data. Dave still working through some errors in ingest of SVDE data – this needs to be resolved before looking for concordance. Has asked Frances for 2015 concordance
        • 2021-04-23 Waiting on indexing of PCC data, have learnt more about the basis for the old OCLC concordance file
        • 2021-05-07 Steven didn't have much luck getting data from SVDE, learning GraphQL endpoint but also problems with timeouts there (HTTP 503)
    • What is the space of Work ids that we might use and their affordances?
      • OCLC Work ids, SVDE Opus (Work), LC Hubs (more than Hubs), what else?
      • Connections to instances, how to query, number
      • 2021-05-07 ACTION - Huda to start analysis
    • Other SVDE entities
      • 2021-05-07 ACTION - Huda will reach out to Jim Hahn about entities other than Works represented in SVDE
    • Publisher authorities/ids
      • At Cornell we haven't tried to connect authorities with publishes
      • LC working on connecting to publisher identifiers - utility is things also published by a publisher
      • Also possible interest in series and awards
      • 2021-04-23 Might be able to use LC publisher ids in BANG!, Steven will look at whether there is a dump available
    • DAG Calls
      • Meeting link
      • Possible questions: How will the BF produced by linky MARC be better than from our current MARC? How would that compare with SVDE data? How do back-end improvements reduce the number of D&A indexing matchings need to be done? What does the use of D&A matchings tell us about the value or prioritization of back-end data improvements? Might be useful to look at D&A wiki and/or ask Frances for the improvements we currently make during indexing2021-05-07 Next week talking about visualization but then planning out sequence of topics: Framework for thinking about discovery questions, possibilities within data, etc.

Linked-Data Authority Support (WP2)

...

  • 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"
    • Folder Link, CFP + Brainstorming
    • 2021-03-26 Abstract accepted, paper due June 25
    • 2031-05-07 Meeting scheduled for 5/13 with group.  Document to capture discussion/references
      • Research paper format: "Word count: Research articles should be between 6,000 and 9,000 words (including notes but not references).". Peer reviewed.  Have emailed KULA folks just to confirm type of article.
  • LD4 Conference 2021 - response on proposals will be announced April 30; conference is July 12-23
    • Discovery - suggestion of discussion form 
      • Huda submitted status of discovery update, BOF for DAG, and discussion of opportunities for effects and use of linked data (60min discussion)
      • 5/7: Received word that affinity groups will be getting reserved time they can use as desired, so may go ahead with BOF format (will need to discuss with co-chair/DAG members)
    • Lynette/Greg/Dave - containerization, should have documented product by then
      • 4/9: Submitted abstract for presentation
    • Lynette – possibly something about the working group, perhaps updated version of code4lib
      • 4/9: Submitted as a lightning talk
    • Document for brainstorming (in case anyone wants to use it)
  • BIBFRAME in Europe workshop - September 21-23 15:00–18:00 CEST = 9am-12noon EST
  • Lynette doing a QA presentation at Samvera partner call in June

Next Meeting(s), anyone out?:

  • 2021-05-07-14 Cancel - too many out