Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review new METS files #55

Open
mikegerber opened this issue Apr 5, 2022 · 3 comments
Open

Review new METS files #55

mikegerber opened this issue Apr 5, 2022 · 3 comments
Assignees
Labels
question Further information is requested

Comments

@mikegerber
Copy link
Member

DEFAULT should now contain IIIF URLs with the max resolution making MAX obsolete.

@mikegerber mikegerber added the question Further information is requested label Apr 5, 2022
@mikegerber mikegerber self-assigned this Apr 5, 2022
@mikegerber
Copy link
Member Author

https://content.staatsbibliothek-berlin.de/dc/PPN1048290832.mets.xml is an example, which contains there URLs for DEFAULT:

    <mets:fileGrp USE="DEFAULT">
      <mets:file ID="FILE_0001_DEFAULT" MIMETYPE="image/jpg">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000001/full/max/0/default.jpg"/>
      </mets:file>
      <mets:file ID="FILE_0002_DEFAULT" MIMETYPE="image/jpg">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000002/full/max/0/default.jpg"/>
      </mets:file>
      <mets:file ID="FILE_0003_DEFAULT" MIMETYPE="image/jpg">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000003/full/max/0/default.jpg"/>
      </mets:file>
    </mets:fileGrp>

ppn2ocr generates these:

    <mets:fileGrp USE="MAX">
      <mets:file ID="FILE_0001_MAX" MIMETYPE="image/tiff">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000001/full/full/0/default.tif"/>
      </mets:file>
      <mets:file ID="FILE_0002_MAX" MIMETYPE="image/tiff">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000002/full/full/0/default.tif"/>
      </mets:file>
      <mets:file ID="FILE_0003_MAX" MIMETYPE="image/tiff">
        <mets:FLocat xmlns:xlink="http://www.w3.org/1999/xlink" LOCTYPE="URL" xlink:href="https://content.staatsbibliothek-berlin.de/dc/PPN1048290832-00000003/full/full/0/default.tif"/>
      </mets:file>
    </mets:fileGrp>

So the difference is:

  • full/max (new original METS) vs full/full (ppn2ocr)
  • JPEG vs TIF

@mikegerber
Copy link
Member Author

  • Image API docs for version 3.0 say that full/max is indeed more correct (full = not cropped, max = maximum size, but not upscaled).
  • The TIFFs returned by our IIIF API are JPEG compressed... So I consider using .jpg or going PNG

@mikegerber
Copy link
Member Author

* The TIFFs returned by our IIIF API are JPEG compressed... So I consider using `.jpg` or going PNG

The question is if these are the "original, untouched TIFFs" (which may be compressed, sadly) or if those are recompressed - something I'd like to avoid here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant