We need to include more fields from marburg for the photo ids as described below:
We uploaded our images (~1,6 m) to Amazon S3 Bucket, and this is how
we did it:
(1) First you have to check if gesperrt exists in
, in this case we do not have the right to share the image.
(2) If does not exist, then can be selected.
(3) If does not exist, the first (last scan of the
image) can be selected.
(4) If does not exist, this means that the image has not yet
been digitized.
2. We have extended the google document. We corrected the translations
and tried to find a general solution (see column Semantics). The problem
was that in our existing relationships in MIDAS between the objects in
CIDOC CRM do not exist. Therefore we used 'E13 Attribute Assignment' in
many cases. This solution will be discussed with KHI and BH. What do you
think about it?
3. Our data can be used for reconciliation. The type of work is in
and the aat vocabulary is in .
We need to include more fields from marburg for the photo ids as described below:
(1) First you have to check ifgesperrt exists in