Skip to content
Islandora Foundation Community edited this page Jul 27, 2022 · 4 revisions

Time/Place

This meeting is held virtually via Zoom, with an open channel for chatter on Slack. Anyone is welcome to join. The hosting can be claimed by anybody with the host ID. The Host ID is in the header of the TAG slack channel.

Chair Roster

These are the core members of TAG and will take on chair of the meeting if there are no volunteers, and will support volunteers who are chairing for the first time:

  • Don
  • Seth πŸͺ‘
  • Rosie
  • Willow

Attendees

  • Seth Shaw (Chair)
  • Jordan Dukart
  • Alan Stanley
  • Don Richards
  • Rosie Le Faive
  • Willow Gillingham
  • Alexander O'Neill
  • Yamil Suarez
  • Adam Vessey
  • Will Panting
  • Rebel Cummings-Sauls
  • Wade Collins
  • Isabella Nikolaidis (Notes)

Agenda

Note that links are to the document repository only. New issues in other repositories or organizations will not appear in this list, and should be added by interested parties directly to the agenda.

  1. https://github.com/Islandora/islandora/security/advisories/GHSA-m58q-qq5h-mgqq
  2. Issue Roundup - Link sorted by recently updated
  3. PR Roundup- Link sorted by recently updated
  4. Review of mailing list
  5. Use-a-Thon at IslandoraCon
  6. Feel free to add more, or add something from Islandora Discussions

Minutes

Issue Roundup

https://github.com/Islandora/islandora/issues/893

  • Rosie: it's really useful to add multi file media
    • have created an associated PR

https://github.com/Islandora/documentation/issues/2138

  • Alexander: was not able to reproduce, seems like a network error

https://github.com/Islandora/documentation/issues/1541

  • install profile doesn't include the default configs stuff, which we're still shipping
  • how do we reconcile Islandora defualts vs profile people get
  • Rosie: install profile is hard to manage, strange code not documented anywhere, and it's behind all the work the community is trying to do in defaults and other things
  • if we can come up with a better way to start up site that could supercede the install profile
  • Don: are we suggesting we go back to what it was before or something else
  • Rosie: This might get running with the CfP we announce - to have a full site.
    • The install profile gives you a full sites worth of configs as well as a composer.json and composer.lock plus some content.
    • It would be deployment independent, you could run it on the Ansible playbook or ISLE.
    • That way as well it would be straightforward to update it.
    • Especially lock file with the updates we'll have to do, and configs as you want to reword stuff/change things do stuff in different ways.
    • It would deprecate the weird code stuff that happens in the install profile, some of that has been extracted out into separate modules.
  • Seth: Deprecate defaults? Refactoring defaults?
    • If defaults is just config we could do all that in the install profile, and then the install profile can be done by isle or the playbook?
  • Don: Install profile could be a glorified config installer?
    • Should be completely barebones from how you deploy it
    • It should install all the needed modules for you and set everything up.
  • Seth: If we lean into the profile, then we deprecate islandora defaults as a module, because all that code would come into the profile.
    • And then PRs will be against install profile.
  • Alexander: One of the proposals we are looking at is move away from the install profile because that's what Drupal is moving away from.
    • Emerging way to have a fully formed, fully functional site that doesn't have the restrictions that an install profile causes.
    • You can only have one going at once with an install profile.
  • Rosie: If you could install islandora on top of an existing site - would be good. To do this we couldn't have an install profile, we would need separate modules that made it clear how to do that.
  • Yamil: You can't install an install profile after the fact -
    • I'm going to launch Islandora 2 on the install profile so what to expect?
  • Alex: The limitations of install profile - harder to update because the set of install profile is initial configs.
    • Modules can be added on top of your install profile.

https://github.com/Islandora/documentation/issues/2140

  • Rosie: associated PR
  • Alan: can help work on the review of this PR
  • Alan: Given that we don't use media as media (media are supposed to be reusable and we don't reuse them), they're more datastreams. As we move to MFM, we're not used to a pile of media.
    • Having a media-less stream? Stick files on the node.
    • Original model was to keep the metadata clear from the file, but the metadata will be contained in the node anyhow.
    • And we don't need FITS and models on media anyways.
  • Alexander: If you are configuring a Drupal 9 site now and adding a field, there's help text to say if this is not a legacy site/field, add a media not a file field. So media is becoming more of a "first-class citizen" in Drupal.
  • Seth: We had also structured this around the PCDM - the impact is representing this data in Fedora
    • re: adding file directly to the node -- instead of doing this, just add the descriptive metadata to the media record, which could essentially give the same effect - make media reusable and nodes are still articles and things of that nature, in line with how Drupal is thinking about it.
    • trying to think Drupal-y
  • Alan: Does Drupal have an opinion about stacking files on the same media?
  • Rosie: It's expected - that's how you work with players and transcripts
    • even OCR
  • Alan: if we're using the MFM model with Wrokbench we can have derivatives and stick that wherever we want to
  • Seth: But paginated content issue?
    • Media that represents a page
    • OCRs attached to it
    • Can't add multiple pages to that media very cleanly
  • Rosie: I have a working sample of media with pages, needs a weight field on it so it works.

https://github.com/Islandora/islandora/issues/891

  • Rosie: Media has a built in thing called thumbail thats not a field.
    • When you're using MFM, it whitescreens because its not a field and our processing assumes field stuff.
    • It would be great if when you looked at your media list it wasn't the default icon.
    • islandora_thumbnail on media, and then rewrite - IF empty: use the file.
    • To do that outside of views, we could if we wanted to take a deeper look at how Drupal thumbnail works
  • Rosie: There's Drupal modules for this too - pdf thumbnail module
  • Seth: Views has built in references to these thumbnails, so you may not recognize it when you want to display the thumbnail because its probably trying to pull in Drupal. This would allow you to play with size/display/context
    • With MFM this would be useful to, to not have a separate thumnail media on your file πŸ‘
  • Rosie: Thumbnail Images in Islandora on wiki

https://github.com/Islandora-Devops/isle-dc/issues/280

  • Rosie: This seems weird - could it be a network error or soemthing
  • Don: may have caught that right after we pushed a PR that had a thing left out of the makefile
  • Don: Fairly certain this has been addressed. If you pull in the latest update you shouldn't have that error

https://github.com/Islandora/documentation/issues/2003

  • Rosie: Old fix that has been merged and now some new issues
  • Alan pointed out some code that should be updated
  • The MFM handler lets you, like with normal derivatives, have a drop down to put the file into because its not going to be your default storage.
  • It wasn't showing file field, but for image you want it to show image fields.

https://github.com/Islandora/documentation/issues/2003

  • Alan: the EVA view ?
  • Reach out on slack to see if we can field any questions

https://github.com/Islandora-Devops/isle-buildkit/issues/217

  • Tom: Can default log levels be set to warning or error wth override via ENV variables?
  • Seth: Turning into a feature request of configurable log levels

https://github.com/Islandora/documentation/issues/2139

  • Documentation Models pages to be created

https://github.com/Islandora/islandora/issues/889

  • Rosei: FunctionalJavascript needs a chromedriver, ran into issues
    • the FunctionalJavascript tests are not running but they display a green checkmark
  • Alexander: did they work? We could run tests locally?
  • Rosie: has anyone done local running of javascript tests?
  • Alexander: Have for modules that are part of islandora
    • you do have to run a Chromedriver
  • leaving documented but unenabled for the time being

https://github.com/Islandora/chullo/issues/97

  • Rosie: Misleading Chullo branches
    • All of our code points to 1.x
    • They're on Crayfish, Crayfish Commons.
  • Seth: All the others are stale branches, was there any release documentation about Chullo that referenced other branches? That would be my only concern.
  • Seth: πŸ‘ to delete
  • Rosie: there are people downloading dev dev (https://packagist.org/packages/islandora/chullo/stats#dev-dev)

https://github.com/Islandora/islandora_ci/issues/13

  • Drupal PDF module isn't ready for Drupal 10 yet so any module will break CI
  • Rosie: We can take the pdf part out of the shared CI and put in islandora and whatever other modules it needs to be in.
  • Seth: Does this break merging?
  • Rosie: No, I've turned it off for Drupal 10.
  • Rosie: Leaving here to revisit later.
  • Seth: A lot of Drupal modules have a Drupal compatibility ticket to point out issues.

https://github.com/Islandora/islandora/issues/888

  • Dependencies Context, PDF are not yet Drupal 10 compatible
  • Drupal 10 for December

Questions

Wade Collins: I have a question regarding best practices for backing up isle-dc installations, specifically, the MariaDB/MySQL databases

  • Using Commvault for our backup software

  • Set up the docker host servers and got the ISLE DC spun up and I opened a ticket with Commvault for best practices for backing up.

  • Commvault basically said we used to have a docker agent and its been deprecated.

  • We're backing up the entire virtual machine that's hosting the dockerized ISLE DC but that doesn't get to backing up the actual database?

  • Don: β€˜make drupal-database-dump' , 'drupal-public-files-dump', 'fcrepo-export'

    • Some make files don't show up in the help file of ISLE
    • using the backup and migrate module from Born digital
      • this simplifies things, can run a drush command to get your backups
    • Rebel: Is this already installed?
    • Don: Backup and migrate is not
  • Don: docker cp : filepath

  • https://docs.docker.com/engine/reference/commandline/cp/

  • Alan: volumes are in /var/lb/docker/volumes

    • If you back that up you've got anything
    • Rosie: If you haven't tested your backups you don't have any πŸ‘€
  • Seth: running ISLE, ISLE opts is still not well documented

  • Rosie 3 open PRs regarding access checks that are also really important.

  • Rosie's CI review: CI fixes also under the PR list - if they're green please merge them.

Quick Link to a Wiki Search in Github

🏠 Home

✍️ Onboarding Checklist

πŸ—ΊοΈ Roadmap

❓ How to maintain this wiki

Committees/Groups

πŸ““ Board of Directors (BOD)

πŸ““ Coordinating Committee (ICC)

πŸ““ Leadership Group (LG)

πŸ““ Technical Advisory Group (TAG)

πŸ““ Code of Conduct Committee

πŸ“š List of Interest Groups

Meetings

πŸ“† Weekly Open Tech Call

πŸ“† Monthly TAG Meetings

πŸ“† Monthly Open Meetings

πŸ“† Biweekly Islandora Coordinating Committee Meetings for ICC members

Camps and Conferences

πŸ“£ Upcoming:

  • No upcoming events

πŸ“£ Past Camps and Conferences

πŸ“… see the Islandora Community Calendar for events and meetings.

Clone this wiki locally