Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Current »

How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

 Click to view telephone/H.323/SIP connection instructions

Telephone:

Meeting ID: 613 720 745

+1 646 876 9923 (US Toll)
+1 669 900 6833 (US Toll)
+1 408 638 0968 (US Toll)
International numbers available: https://psu.zoom.us/zoomconference?m=UZ_PRwQ56TNX1pDIsdDInAu8XPVqzlX3

H.323:

Meeting ID: 613 720 745

162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
69.174.57.160 (Canada)

SIP: 613720745@zoomcrc.com

Time: 9:00am PDT / Noon EDT

Moderator: tamsin woo

Notetaker: James Griffin

Attendees:


Agenda

  1. Roll call by timezone per following order - ensure notetaker is present (moderator)

    1. folks outside North and South America

    2. Eastern timezone

    3. Central timezone

    4. Mountain timezone

    5. Pacific timezone

    6. folks who were missed or who dialed in during roll call

    7. Remind everyone to sign in on agenda.
    8. Welcome all newcomers!
  2. Agenda (moderator)
    1. Call for new agenda items (moderator)
    2. Add agenda items here
  3. Moderator & notetaker for next time
    1. Moderator:
    2. Notetaker:
  4. After call, this week's notetaker should create the agenda for the next call:
    1. Open template agenda titled "Samvera Tech Call 2019-xx-xx"

    2. Click on ... in the top right corner, and select copy.
    3. Popup will open for location. It should contain: 
      1. Space: Samvera
      2. Parent page: 2019
    4. Select copy. New page should be created.
    5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.
  5. PR Review
    1. Review issues:
    2. PR review coordinator for next time: 


Notes

Outstanding Wings PRs are reviewed

There were some PRs which were stale and closed

Should they be reviewed?

If somebody is asking for one of them to be reviewed, then we should; otherwise if no one is advocating for a review the perhaps we should not

#3479: LaRita authored a sizeable PR

It never received a review

Chris asked LaRita about this in a GitHub comment

Julie: Has one waiting for review, but has merge conflicts which shall need to be reviewed (#3760)

Wanted a more thorough review before continuing to work to resolve conflicts upstream

Rob Kaufman approved of it more than one month ago

Did nothing substantive, but did introduce changes which dismissed the approving review

Will need to resolve conflicts before approving of the PR?

Questions regarding riiif Gem support arose during the review

If users haven't installed riiif, there might be an issue; this might need to be tested

Inline the ImageMagickInfoExtractor into the Hyrax namespace in order to avoid a hard dependency for Riiif::ImageMagickInfoExtractor

Characterization information isn't extracted by the FITS alone; hence the ImageInfoExtractor step is needed in order to resolve this

Tom: It's okay to special in the Hyrax namespace temporarily

Then, introduce this into hydra_works and pin to the new release

Ultimately, the goal is that hydra_works won't exist after Wings for Hyrax work is completed

PR also makes assumptions about the image format (currently only handles JPEG and PNG formats)

It does make sense; clients can only request these formats from the Riiif IIIF Image Server

Developers might use another IIIF Image Server; they may wish to request a different format from that server

IP might return pyramidal TIFFs; should we be concerned about these other cases?

A note was made on GitHub; Julie will investigate this further with other possible viewers for a potential unhandled format

Might also be able to just comment where there might be concerns; ultimately, those using different IIIF Image Servers are likely to undertake heavy customization regardless







  • No labels