Versions Compared

Old Version 2

changes.mady.by.user Huda Khan

Saved on

compared with

New Version 3

changes.mady.by.user Huda Khan

Saved on

Key

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

...

  • Knowledge panels and entity pages
  • Discussion
    • Question: Are there user stats around the use of the info button?
      • We can ask Melissa
    • Question: How might the use of external data affect performance?
      • So far, the page display seems to be fine for knowledge panels.  Improvement may be possible but doesn't seem out of range of acceptable.
    • Comment: Dealing with data timeouts, etc.
      • Page can be configured to not display info if request takes too long. Can find graceful ways to fail.
    • Fred appreciated how these features take the user back to the catalog results and tie into digital collections and repositories
    • Influence relationships
      • How is this information defined?
      • The list seems a bit random. 
      • Comment: Could possibly bring in other pieces of this work and review how the influence portion could be displayed/which data to use 
    • Huda: Ok to bring this back to the group in August after FOLIO to start thinking about how we might implement?
      • Reasonable to start with knowledge panel work first and then bring in entity page if group agrees?
        • Seemed like a yes (as far as discussing it in August)
    • Slides link (included above) will be forwarded (by Lenora) with User Reps group again.  Additional comments and feedback welcome. Demo link to be shared after LD4P3 web server updated with code

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
    • 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-04-02 Tim has implemented a D3 based graphical representation for Influenced by and influence for. Currently not limit to the number of related entities shown (e.g. many many influence-for for William Faulkner). When no examples shown the header is not shown, where there is no image (or not a png or jpg) then a circle is shown. Discussion:
        • Agreement that we should put a limit (perhaps 12) on the number of influenced-by or influence-for entities, ideally with a count of total and link to show all
        • Debate about best way to show all for long lists
        • Suggestion that we need to make the data source plain because the data is debatable/subjective and often incomplete
        • Would be good to test which related entities are in catalog and add links to the appropriate info pages
        • Ideally we will not show the Influence tab when there is no data for influenced-by or influence-for entities
    • Considering KPAOW zero (streamlined knowledge panels). Have begun discussing what should go in a streamlined version.
      •  Huda Khan Scheduled meeting with D&A reps April 9th, 9-10 (Moved the LD4P3 meeting to this time)
        • Neither Jason nor Simeon are available for the meeting
    • Usability testing for DASH
      • Getting ready for usability tests in April
      • Need to finalize usability tasks for both authors and subjects
      • 2021-04-02 - Four people responded to request and have scheduled tests for next week (Apr 7 & 9), will review entity pages
    • User reps D&A meeting: Need to re-follow up
      • Slides:
      • Good to have knowledge panel lite mockups or examples ready to show
      • 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
          • 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
        • 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. 
          • 2021-03-26 - Other CUL staff met a couple of weeks ago. Examples where print and e-resource versions have differing metadata quality. Can we connect the resources better and/or copy metadata from one to the other? Has connection to our work to identify different versions. Nothing for LD4P3 to do until they have come up with appropriate examples
      • How do our new mockups support ideas of local overrides or correction to address DEI issues?
        • Question of process for reporting and dealing with errors
        • Use of wikidata means that individuals can make some changes there - direct citation in the data makes that plain and more easily actionable
      • Subject headings
        • Currently we don't show how many other headings a sub-heading appears in, this could be calculated
        • E.g. if someone is looking at "Architecture - Norway" would it be useful to see other headings that include Norway. Or would a use simply search for Norway?
        • Questions about whether some types of subheading (such as temporal or spatial) might be more usefully connect than others
        • Perhaps see if this comes up in the testing

...