Feature #1456


Added by Alexander Watzinger 28 days ago. Updated 8 days ago.

In Progress
Target version:
Start date:
Estimated time:
16.00 h


The SHAHI project needs to enter objects outside an archeological context.
  • We will implement the (new) objects using the E22 CRM class, accessible via the object tab
  • Already implemented E22 objects for archeological finds will still be handled separately inside the context of archeological sub units



Updated by Alexander Watzinger 26 days ago

  • Description updated (diff)

Updating description after discussing it at meeting. Special thanks to Stefan for looking into it and coming up with a good solution.


Updated by Alexander Watzinger 17 days ago

  • Estimated time set to 16.00 h
  • Assignee set to Alexander Watzinger
  • Status changed from Acknowledged to In Progress
  • Subject changed from Using objects outside of archeological context to Artificial objects

Updated by Alexander Watzinger 17 days ago

Artificial objects are implemented and can be tested at the development demo:

They will be without places/map in the first version because we have to rethink our map presentations before, e.g. should they displayed beside the place geometries or do we display them separately.


Updated by Alexander Watzinger 9 days ago

  • Subject changed from Artificial objects to Artifacts

Updated by Stefan Eichert 8 days ago

I have seen that artifacts have their own type tree. We should discuss if we better use the find type tree for them, as they are actually the same. The difference regards only the fact that finds are conceptually located below strat units and artifacts not. But by definition both are artifacts. Finds could also be listed then in the artifacts/objects tab.


Updated by Alexander Watzinger 8 days ago

@ Stefan: interesting thought, we may can discuss this tomorrow at the workshop

Also available in: Atom PDF