Skip to content

Latest commit

 

History

History
106 lines (89 loc) · 6.62 KB

2021-05-03.md

File metadata and controls

106 lines (89 loc) · 6.62 KB

Islandora Metadata Interest Group Agenda

Monday, May 3, 2021, 1-2pm EST

  • Chair: Kristina Spurgin
  • Notetaker: Paige Morfitt

Join Us!

Working Documents:

Attending:

  • Kristina Spurgin
  • Paige Morfitt
  • Karen Gross Benko
  • Mike Bolam
  • Christopher Day
  • Gabi
  • Alex Kent
  • Danny Lamb
  • Rosie Le Faive
  • Matthew Lincoln
  • Lisa McFall
  • Alexander O’Neill
  • Mandy Ryan
  • Seth Shaw

Agenda:

  • Announcements
    • Glossary terms
  • Decision: indicating deprecated terms in Agent field (examples)
  • Demo/walkthrough of default work
  • Post-sprint survey
  • Round table

Notes

  • Announcements

    • Last Tuesday's open meeting.
    • Glossary is in the works -- to help with terminology regarding Islandora 8.
      • It’s not part of the official documentation, but it’ll be a working document.
      • If someone talks about something, or uses a term you are unfamiliar with, please feel free to ask for clarification so we can add it to the glossary.
      • If you don’t feel comfortable asking during the meeting, feel free to add in chat or in Slack.

  • Decision: indicating deprecated terms in Agent field examples

    • Deprecated terms are used to accommodate people who are using legacy data.
    • Removed relator codes form the display (everything in parentheses which included deprecated notes).
      • Option 1 - Could keep depreciation note in the display (pro: it’s in your face when you’re creating metadata, con: displays to the public). This could encourage you to remediate your metadata.
      • Option 2. Don’t add to the list, but add note to field documentation of depreciation terms. (The little paragraph on the back end would mention the depreciation note) (pro: not shown to public, con: not as “in your face”) -- metadata entry perspective, this may cause some worry
    • Controlled access module was meant to be stand-alone.
    • Suggest get feedback regarding this, if this list should be stand-alone or not. Would like to indicate in the module notes.
    • If depreciation roles appear to the public, it could be okay. It could indicate to users to search by another term (so if artist is deprecated and it says so on the public side, it could hint to users to use a different term to search by.).
    • If later, you change your mind, it’s pretty simple to remove the deprecation note (which we’d need to add to documentation).

  • Demo/walkthrough of default work : Post-sprint to-do list

    • Last meeting we changed “Linked Agent” to “Agent”. This just changed the display label. The field machine name will remain the same.
    • Since last meeting, fixed RDF mappings.
    • Synchronizing singular v. plural names as well as capitalization.
      • It was brought up that librarians prefer plural terms. For terms, it makes sense, but labels?
      • Schema perspective, it’s singular, because you’re giving a singular title. Even if we have multiple tags to a field, it still represents a singular tag (multiple dates, you’re still referencing a date).
      • Potential that users may not care as much about.
      • In RDA -- no standard for public display.
    • Coordinates (text)
      • It allows keeping data without having to make it into the specific coordinates format.
      • It also could instigate a clean-up if someone saw this field in use -- they’d know to clean it.
    • Place Published (MARC country) v. Place Published (country)
      • If users don’t know who MARC is… maybe change label to place country, or Place of Publication.
    • Subjects -- renamed fields to be consistent.
      • If they’re not separated out into topics (not separated out , they will be added into topical).
      • Could we have a generic ‘subject’ field to accommodate people who don’t have time to clean up their spreadsheets, and split subjects out / to accommodate legacy metadata?
      • There is a lot of messiness regarding I7 ingest using spreadsheets. Having something that’s not trying to mimic MARC may be helpful.
      • Will add generic subject field.
    • Once fields are set up, the form is very long.
      • Put required fields at the top in the required section ( title and model).
      • Added field groups so things you may not use all the time are together so you could collapse them (and it’s a drag and drop so you can easily change the form).
    • Created a full title field (which is a long text field).
      • Alternative titles : full title could be single value, from transcribing off the piece, and alternative titles should be repeatable (multi-valued) to accommodate the various abbreviations/versioning of titles.
    • Display hints -- people are moving away from display hints -- our add to documentation where to go.
    • Language
      • Drupal only set up to show english -- unable to set up a note to indicate where you are indicating the drupal language not item language.
    • Access terms -- (limited access/limited view)
      • If people are using taxonomy, it may be harmful to use.
      • The number of items - for small site, taxonomy is fine, but as you add more items, you’ll get more problems.
      • Suggested -- to not make this a taxonomy because it’s messy. It does not scale.

  • For next time:

Next Meeting:

  • May 17, 2021