You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been looking through the inconsistencies you have found in the catalog and there is a strange situation going on with tifs.
Usually, uploading tifs into Azoulay will generate associated jpgs which all end up in Nabu.
However, as you have pointed out with the JK1 collection, the tifs are not generating jpgs and instead some of them have generated 2-page pdf's.
This has then resulted in the notification of no jpeg files existing in the catalog.
I have emailed you one of the original tifs JK1-REB201909-062 for you to have a look at (github does not accept tif files).
I also tried uploading the tifs again to see if they generated jpg's but it did not change anything.
We would like to work out why these pdf's have been created and happened to generating jpgs to go with the tifs.
Some of the other files in the list also should have jpgs generated from tifs such as:
VCBD-024-006, 007, 011
In this case, these three files have ended up with a pdf, while all of the other files have a jpg.
The other collection with inconsistencies of this type is CLC with these four files showing strange naming and also a pdf generated instead of jpg.
I've had a look through the above issues listed by Jodie and I think I'm managing to fix them by creating the tifs again and re-ingesting them to Nabu. Seems to be working so far...
However, our jpg script is definitely acting buggy, seems to be working inconsistently. E.g. I put some tifs in today and they went into Nabu but jpgs were not created.
@johnf if you have a chance to look at it, see if anything looks amiss...
Essentially it should just create a jpg version of any tif file that is put into Nabu, (and then archive both tif & jpg).
let us know if you need more info
We have been looking through the inconsistencies you have found in the catalog and there is a strange situation going on with tifs.
Usually, uploading tifs into Azoulay will generate associated jpgs which all end up in Nabu.
However, as you have pointed out with the JK1 collection, the tifs are not generating jpgs and instead some of them have generated 2-page pdf's.
This has then resulted in the notification of no jpeg files existing in the catalog.
I have emailed you one of the original tifs JK1-REB201909-062 for you to have a look at (github does not accept tif files).
I also tried uploading the tifs again to see if they generated jpg's but it did not change anything.
We would like to work out why these pdf's have been created and happened to generating jpgs to go with the tifs.
Some of the other files in the list also should have jpgs generated from tifs such as:
VCBD-024-006, 007, 011
In this case, these three files have ended up with a pdf, while all of the other files have a jpg.
The other collection with inconsistencies of this type is CLC with these four files showing strange naming and also a pdf generated instead of jpg.
CLC-JLMM_Yirara1981-12.jpgf.tif image/jpeg 48.8 MB (https://catalog.paradisec.org.au/collections/CLC/items/JLMM_Yirara1981/essences/1116346)
CLC-JLMM_Yirara1981-12.pdf application/pdf 56.2 MB
(https://catalog.paradisec.org.au/collections/CLC/items/JLMM_Yirara1981/essences/1386865)
CLC-JLMM_Yirara1981-12.tif image/tiff 48.8 MB (https://catalog.paradisec.org.au/collections/CLC/items/JLMM_Yirara1981/essences/1386862)
CLC-JLMM_Yirara1981-12.tiff.tif image/tiff 48.8 MB (https://catalog.paradisec.org.au/collections/CLC/items/JLMM_Yirara1981/essences/1116345)
The text was updated successfully, but these errors were encountered: