Skip to content

Latest commit

 

History

History
105 lines (92 loc) · 7.07 KB

2024-08-12.md

File metadata and controls

105 lines (92 loc) · 7.07 KB

Islandora Metadata Interest Group Agenda

Monday, August 12, 2024, 1-2pm EDT

Join Us Virtually!

Chair Roster

  • Chris Day 🤿
  • Rosie Le Faive 🪑
  • Paige Morfitt 📝

Working Documents:

Attending:

  • Rosie
  • Paige
  • Tyrica Terry Kapral
  • Tracy Tolf
  • Dani Kroon
  • Mike Bolam
  • Meaghan Else Cash
  • Seth Shaw
  • Ann Marie Mesco
  • Kara Hart

Agenda:

  • Announcements
  • Changes to Starter Site
  • Revisions by Default on Taxonomy Terms
  • Typed Relation With Display Name
  • Equations in Abstract
  • Title - priorities?
  • Open Discussion
  • Glossary Review

Notes:

  • Announcements: DrupalCon in Barcelona.

  • Starter Site changes: No changes. Nothing that will impact any metadata

  • Taxonomy Terms: Turning on revisions by default

    • In Drupal, they created a way to make revisions in metadata terms
    • Question: Do we want to turn this on by default on all/any of our vocabularies?
      • Go to genre taxonomy, select a term, and click "revisions". Automatically the content will show the new name. You click the 'revisions' tab, it will show you when the term was revised. It also allows you to revert the term back. The revert puts the old value back in addition to the new value (it does not rewind or rewrite).
    • Question: What does the revision do?
      • A log of changes to taxonomy terms. It is useful to see, however you do need to do some digging to see what has been changed. But it would keep us honest and be available for auditing/for quality control if you have a student change terms you can check their revisions. It does take more space in the database. People already have the ability to do this, but it's about making it a default.
      • This would only be if the taxonomy terms changes, but changing the data on the object wouldn't change anything. This would only track the taxonomy term change (so if you move something embargoed out of embargoed, it would not be tracked -- when you change a person's name in the taxonomy, you have in theory changed the metadata in all the records that use that term. the node doesn't know that).
    • You don't have to do this for every taxonomy either.
    • It would be helpful to look at our metadata as a series of links.
    • Rosie will put up a pull request to default making revisions on taxonomies

  • Typed Relation With Display Name

    • Rosie made a Display Name field in Typed Relation.
    • If you have a name, but the name has been changed or you want to display something in a more human-readable form (example, Lastname,FirstName (YYYY- ) but you want FirstName LastName) Display Name Field can change that.
    • The display name is optional. If you don't use it, it will default to the field.
    • This is a way to associate a name with a person at the time. If you want to bulk change it does make it a bit more challenging, but its no more challenging than other bulk changing.
    • If you want to adapt this to your site, you cannot change the Type of field easily. You need to make a new field, export data (workbench) reimport that data via workbench, and set up your facets and all that.
    • Is there interest in this in place of contributors typed relation field? Workbench integration is important. Rosie hasn't done all the tests yet.
    • What you would put into your workbench:
      • relators:aut:person:Rosie Le Faive@Lefaive,R where everything after "@" is the display name and "@" is the delimiter.

  • Equations in abstracts

    • You cannot add special characters to the title ( but we can in abstracts)
    • There is a module called MathJax that lets you write in LaTeX and renders it pretty.
    • This works for screen readers
    • Concern: you can turn stuff off from the starter site, but how much do we want to enable upfront vs. having recipes for IR? This is a bit nichefor IR thing that some institutions may not need.
      • It would be good to have an recipe for IR for the starter site. The IR group has had come conversation about this, however it's unclear the conversation about it.
    • Question: how does abstract work with non-latin text? It might already be built in.
    • The ability to have title field that accommodates this would be nice (example, a title in arabic, or a title with math equations in it).
    • Th eidea for a recipy works. But where would we store it? Should we store it? Should we put it in our cookbook? Does it need tobbe Drupal, or just an "install this module"?
    • We could put this in the islandora documentation recipe page

  • Title

    • Rosie was working on Title field and replicating MODS
    • Lets vote on priorities:
      • italics and bold
      • unlv uses : https://www.drupal.org/project/html_title
        • Does this make a rich ield? It does not change field type (drupal will now let you do that), but allows you to put in some tags you allow, then it will convince drupal to render it as html instead of escaping it (as it currently does)
      • Will it change tab title of webpage? unclear
    • Rosie will text out and do a PR

  • Open Discussion

    • ASU - working for new content model for scholarly content. It's mostly ready to go other than styling and migration code.
      • Instead of having complex object, the structure, they have a media reference field opposed to media pointing to node.
      • This helps with google analytics, so anytime someone clicked on the child of an object, google analytics now counts it as visiting the parent, opposed to earlier the child was separate from the parent.
      • For thumbnails, using drupal thumbnail system opposed to islandora derivatives. With drupal, there is a module that allows you to do documents.
    • PEI -mapping data object
    • Whitman - lots of clean up of metadata on the back end

  • Glossary Work!

    • GUI, Linked Agent, Islandora Model

Next meeting

August 26, 2024