Project

General

Profile

Actions

Feature #2581

open

FemCare: Import of archeological data

Added by Bernhard Koschiček-Krombholz 5 months ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Category:
Data import/export
Target version:
Start date:
2025-07-23
Estimated time:

Description

For the FemCare project, we received parts of the archeological data to prepare an import script.

Branch: feature/femcare-import

Actions #1

Updated by Bernhard Koschiček-Krombholz 5 months ago

  • Status changed from Assigned to In Progress
Actions #2

Updated by Bernhard Koschiček-Krombholz 5 months ago

  • Status changed from In Progress to Resolved

Technically wise, it is done.

Something to keep in mind is that I had to install a new library to handle .docx (python3-docx). It is a Debian package, but since we don't need it anywhere else. I think about handling the .docx files outside the import script (e.g. transform the needed data into a CSV) and then we don't need the package in the OpenAtlas installation.

Issues from the data:
  • Following SE doesn't have a Feature linked to it, or are linked to "Objekt 0" which is not in the object list
    • 1, 2, 92, 171, 175, 456, 462, 907, 908, 909, 915
  • Finds with unclear SE
    • 486, 493, 757, 758
  • Finds with multiple SE
    • 751
  • Finds linked to SE with "Objekt 0" (should be cleared when first issue is solved)
    • 1, 2, 3, 4, 5, 6, 7, 8, 10, 62, 63, 68, 207, 231, 232, 300, 318, 331, 332, 1657, 1658
    • All finds, which have no SE or Feature, is automatically attached to the place

Next step is waiting for the additional Ind. files and the images.

Actions #3

Updated by Bernhard Koschiček-Krombholz 5 months ago

  • Description updated (diff)
Actions #4

Updated by Alexander Watzinger 5 months ago

Thank you for this.

About additional software needed to import project specific data:
I recommend to document it (at the script and/or manual) but not to include the libraries in the application (no additional instruction in the install notes).
It really depends on the situation, if it would be a generic function also used by other projects (e.g. imports from Vocabs) I would do it differently.
But I guess you see it similar anyway.

Actions #5

Updated by Bernhard Koschiček-Krombholz 3 months ago

  • Status changed from Resolved to In Progress

We got the additional data and can start to include it.

Actions #6

Updated by Bernhard Koschiček-Krombholz about 1 month ago

I included all available and reasonable data from my perspective.

The next step is to meet with @Michaela Binder and discuss changes and additional information, e.g.
  • License of files -> Will be discussed
  • Public viewable? -> Yes
  • Creator/license holder -> LH Novetus
  • Split some types in reasonable units (most likely with a new script) -> Dislocation and Position
  • Are the "Fundfotos" somewhere documented? -> Yes, there should be a Excel
  • Add Probe type again with Fundnummer
  • Add Fundnummer of SE
  • New type for files: Grabung, Skelettmännchen, Entzeerte Wirbelsäule, Pathologie
  • English is good, so all type should be english
Actions #7

Updated by Alexander Watzinger about 1 month ago

  • Target version changed from 9.2.0 to 9.1.0
Actions #8

Updated by Alexander Watzinger about 1 month ago

  • Target version changed from 9.1.0 to Administrative
Actions

Also available in: Atom PDF