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
Use case: I'm running CONTENTdm migrations right now, and just ran into an issue where, of a 619-item image collection, 614 are JPGs and 5 are JP2s. I failed to notice the JP2s, and attempted to ingest the whole set as Basic Images, which of course meant that the five JP2s were not ingested.
In migrations where the source collection contains a mix of content models, it would be helpful to create subdirectories in the output directory, so that objects with different filetypes were appropriately grouped. Should be doable with a post-write hook, I think?
e.g. Right now, my images are all poured into the directory herbarium_output. With the proposed post-write hook, the JPGs would get written to herbarium_output/jpg and the JP2s would go to herbarium_output/jp2.
The text was updated successfully, but these errors were encountered:
Use case: I'm running CONTENTdm migrations right now, and just ran into an issue where, of a 619-item image collection, 614 are JPGs and 5 are JP2s. I failed to notice the JP2s, and attempted to ingest the whole set as Basic Images, which of course meant that the five JP2s were not ingested.
In migrations where the source collection contains a mix of content models, it would be helpful to create subdirectories in the output directory, so that objects with different filetypes were appropriately grouped. Should be doable with a post-write hook, I think?
e.g. Right now, my images are all poured into the directory
herbarium_output
. With the proposed post-write hook, the JPGs would get written toherbarium_output/jpg
and the JP2s would go toherbarium_output/jp2
.The text was updated successfully, but these errors were encountered: