...
- 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)
- 2021-06-11: At impasse. new modeling is represented in GraphQL data but fuller data are in RDF. Need to talk to SVDE when have QA/Sinopia conversation. Asked for test data but unsure when we'll have it all. Could consider doing this via Stanford Institutional data - though not ideal. ACTION: Steven will ping Anna to inquire on existing thread
- 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
- Other SVDE entities
- 2021-05-07 ACTION - Huda will reach out to Jim Hahn about entities other than Works represented in SVDE - DONE
- Summarized here: Jamboard link - U Penn Enriched Marc: Work Ids in 996 Field. 1.2 million with OCLC Work IDs in > 1 description. ~3.9 million with OCLC Work IDs in only one record.
- 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
- 2021-06-04
- To plan BANG! we need to think about what can be done with the available data. Perhaps take some concrete examples to consider what LC and SVDE data might give us, no longer sure what we could do with current OCLC works data (hope that entity work will provide new data later)
- What about providing users with better access using alternative labels etc. that might better match their expectations, including different languages via VIAF connections. Much of our catalog data around languages is very bad because we use roman transliterations based on LC rules that are not well sync'd with actual practices in other locales.
- Other possible datasets? Wikidata information is quite sparse (see jamboard). We get Syndetics ToC data for the catalog now, are there other structured data sources for ToC? Perhaps also look at wikicite – could suggest articles even if we don't generally have article level data. ACTION - Huda to ask Jesse whether there are any open structured datasets for ToC, even if much smaller.
- 2021-06-11
- Huda asked Jesse about open structured datasets.
- Huda reached out to Filip Jakobsen from Samhaeng; asked whether anything we can learn about use cases around people wanting to search across institutions to see what works exist (in ReSHARE capacity); Filip made two points: people do not benefit from looking at separate pages for Works and Instances (e.g.: conceptual distinction is not useful for users); users do not want multiple pages per institutions that has that work. If 35 instances that are same across institutions, they don't care for them to be separated. Context here is ILL – and wonder whether that would be true in local library's catalog. Filip had diagram that showed mapping b/t hubs and opi (opuses). ACTION: look at what works are and how would we map concrete examples... can you walk thru end-to-end representation of information for a few concrete examples.
- 2021-06-25
- Huda will ask Jesse again (but after or on July 1st) about other open structured datasets for table of contents information.
- Filip forwarded link to ReSHARE use cases/UX work: https://projects.samhaeng.com/1006/d/1001/ (documents links at various sections)
- Steven will look at what works data we have in the last SVDE converted dataset in DAVE for Cornell
- 2021-07-02
- No update
- 2021-07-09
- Beginning to form some kind of plan regarding explorations:(BANG! Data Analysis)
- Working through a concrete example for LOC Hubs, ShareVDE Super works/Opuses
- Wikidata properties around works: supplement what is visible/possible
- Visualize or query ShareVDE PCC/Cornell (from a few years ago) relationships around different identifiers: ISBNs/LCCNs/OCLC Work IDs. PCC portion seems to have been updated in Dave's Fuseki server(Queries still show same numbers as before so may need to revisit)
- Follow up regarding OCLC Entity Backbone new Work API
- Collect user stories/related work around viewing works/instances (multiple related entities, including from different institutions): ShareVDE/ReShare work
- Meeting with Jesse next Monday to go over Table of Contents sources
- Beginning to form some kind of plan regarding explorations:(BANG! Data Analysis)
- DAG Calls
- 2021-06-25 Discussion on outputs from DAG calls, hope to get KP white paper completed over the summer, and then the "lord of the rings" (to bind them all) spreadsheet
- 2021-07-06 What to do during the conference? 7/20 canceled (because during conference)
...
Next Meeting(s), anyone out?:
- 2021-07-1616
- 2021-07-23 Jason out