Actions
Feature #2466
closedAPI: Export files with ARCHE RDF metadata
Start date:
2025-02-03
Estimated time:
Description
As preparation for the archiving process (#2372) we met the ARCHE team. It should be possible to extract files with RDF metadata with the ARCHE tags:
- acdh:hasTitle - title of entity, can be the file name (see below) or something else, multiple languages possible and alternative titles can be included as well with acdh:hasAlternativeTitle
- acdh:hasIdentifier - includes ARCHE IDs, as well as any external IDs in the form of an URI
- acdh:hasCategory - values come from https://vocabs.acdh.oeaw.ac.at/arche_category/en/
- acdh:hasMetadataCreator - those responsible for entering the metadata, can be multiple
- acdh:hasOwner -
- acdh:hasRightsHolder -
- acdh:hasLicensor -
- acdh:hasLicense -
- acdh:isPartOf - except for instances of acdh:TopCollection, every other entity in ARCHE is required to be part of a (top)collection (see section how to structure files)
- acdh:hasDepositor - as designated in deposition agreement
(There are more to fill out, but these are the required ones)
Mateusz sent the following resources for the creation/validation of the RDF:
- All ARCHE tags
https://arche.acdh.oeaw.ac.at/browser/api/rootTable/en - Crawler to test files
https://github.com/acdh-oeaw/arche-metadata-crawler/blob/master/docs/walktrough.md
https://github.com/acdh-oeaw/arche-metadata-crawler/blob/master/docs/metadata_formats.md#vertical-metadata-file
https://github.com/acdh-oeaw/arche-metadata-crawler/blob/master/docs/metadata_formats.md#rdf-metadata-file - Test ingest of data
https://github.com/acdh-oeaw/arche-ingest/?tab=readme-ov-file#runtime-environment
- Add special exact matches for ARCHE, see Appendix 2
- Add acdh:TopCollection
We also include an option to see which files have no license, creator, license holder, owner etc.
And a thing is also to organize the files with the metadata by resource type.
Updated by Bernhard Koschiček-Krombholz 11 months ago
- Description updated (diff)
- Target version changed from 8.15.0 to 8.12.0
Updated by Bernhard Koschiček-Krombholz 11 months ago
- Related to Feature #2372: API: Archiving OpenAtlas with ARCHE added
Updated by Bernhard Koschiček-Krombholz 11 months ago
- Subject changed from API: ARCHE export to API: export in ARCHE RDF/CSV
- Description updated (diff)
Updated by Bernhard Koschiček-Krombholz 11 months ago
- Description updated (diff)
Updated by Bernhard Koschiček-Krombholz 11 months ago
- Assignee deleted (
Bernhard Koschiček-Krombholz) - Target version changed from 8.12.0 to 8.15.0
Updated by Bernhard Koschiček-Krombholz 7 months ago
- Description updated (diff)
- Assignee set to Bernhard Koschiček-Krombholz
Updated by Bernhard Koschiček-Krombholz 7 months ago
- Subject changed from API: export in ARCHE RDF/CSV to API: export files with ARCHE RDF metadata
- Description updated (diff)
Updated by Bernhard Koschiček-Krombholz 7 months ago
Also include a description field, where additional information for related entities are entered as text.
Updated by Bernhard Koschiček-Krombholz 6 months ago
- Status changed from Acknowledged to Closed
This is partly closed. The functionality is here, but fine-tuning with the ARCHE Team has to be happened.
Updated by Bernhard Koschiček-Krombholz 6 months ago
- Related to Feature #2568: Admin interface for generating ARCHE dumps added
Updated by Bernhard Koschiček-Krombholz 6 months ago
- Missing entries:
- metadata creator should be user like g.logger.get_log_info(entity.id) but this needs way too long (each file need an extra SQL query)
- descriptions should also include information about the linked entities like places and persons
- spatial coverage: if an image is linked to a place/artifact and the top level of this entity is a place with geonames, then take the geonames link. This will be very expensive.
Updated by Alexander Watzinger 6 months ago
- Subject changed from API: export files with ARCHE RDF metadata to API: Export files with ARCHE RDF metadata
Updated by Alexander Watzinger 5 months ago
- Target version changed from 8.15.0 to 8.13.0
Updated by Alexander Watzinger 5 months ago
- Target version changed from 8.13.0 to 8.15.0
Updated by Alexander Watzinger 4 months ago
- Status changed from Closed to Resolved
Updated by Bernhard Koschiček-Krombholz 3 months ago
- Status changed from Resolved to Closed
Actions