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 some data providers that send the images directly to us, for example in the latest case we had around 15K images that we wanted to load to the image-service then update the dwca accordingly via updating imageIdentifer in them.
We tried to use admin tools section Imports image files from local directory and specify the DR in metadata section but as per code it adds this DR value to the meta-data table with the source of SystemDefined and ti doesn't matter if we write data_resource_uid or dataResourceUid
And this field is not searchable in the UI.
The goal here is to load those images for a DR directly into image-service and then search them through UI and download the CSV and update the DwCA to run through the pipelines.
This issue is related to #183 and I think if that one gets addressed, this issue will be resolved as we'll use the S3 folder approach.
The text was updated successfully, but these errors were encountered:
We have some data providers that send the images directly to us, for example in the latest case we had around 15K images that we wanted to load to the image-service then update the dwca accordingly via updating imageIdentifer in them.
We tried to use admin tools section
Imports image files from local directory
and specify the DR in metadata section but as per code it adds this DR value to the meta-data table with the source ofSystemDefined
and ti doesn't matter if we writedata_resource_uid
ordataResourceUid
image-service/grails-app/services/au/org/ala/images/ImageService.groovy
Line 1058 in 43f1a4b
And this field is not searchable in the UI.
The goal here is to load those images for a DR directly into image-service and then search them through UI and download the CSV and update the DwCA to run through the pipelines.
This issue is related to #183 and I think if that one gets addressed, this issue will be resolved as we'll use the S3 folder approach.
The text was updated successfully, but these errors were encountered: