Project

General

Profile

Feature #1215

Time spans for types

Added by Stefan Eichert over 1 year ago. Updated 4 months ago.

Status:
Closed
Priority:
Low
Category:
Backend
Target version:
Start date:
2020-04-24
Estimated time:

Description

In addition to files and external references for types, it would be beneficial to also be able to store temporal information with a type. Just the way we do it with other entities. E.g. a certain type of a find "Crescent Shaped Temple Ring" that occurs between 850 and 1050 should include this temporal information.

These time spans should only apply to custom types. One solution could be to turn this option on when creating a new custom type. Another could be to create a new type-type like the value type.
Or we create a system type like "actor actor relation" for this, then all type trees of this would be under one hood.

Manual text proposal:

Typochronology types:
These types allow to define a timespan (earliest/latest begin and earliest/latest end) for each entry. This mostly applies to archaeological or art history respectively architectural types. 
One example would be chronological groups for certain archaeological material cultures. Enamelled disc brooches for example would be linked to a type "Carantanian C3" This type would have the timespan from 900 to 1000. 
Another example would be to link an E22 Sword to the type "Petersen X" that would have a timespan 900 to 1000.

This way objects (physical things E18 or E22) that do not have their own timespan defined can be traced chronologically via these chronological types.

+1 Stefan


Related issues

Related to Feature #1091: Reference systems for typesClosed2020-11-23Actions

History

#1

Updated by Stefan Eichert over 1 year ago

#2

Updated by Stefan Eichert over 1 year ago

#3

Updated by Stefan Eichert over 1 year ago

#4

Updated by Alexander Watzinger over 1 year ago

  • Target version set to 6.0.0
  • Assignee set to Stefan Eichert
  • Status changed from New to Acknowledged
  • Category set to Backend
  • Description updated (diff)

@ Stefan, thank you for reporting and explaining it to me. As soon as prerequisites are fulfilled (please put both in the description) you can remove yourself as assignee and leave assignee empty.

#5

Updated by Stefan Eichert over 1 year ago

These timespans should only apply to custom types. One solution could be to turn this option on when creating a new custom type. Another could be to create a new type-type like the value type. However if you have other ideas, we can of course discuss them.

Regarding the manual text, here a first proposal:

Typochronology types:
These types allow to define a timespan (earliest/latest begin and earliest/latest end) for each entry. This mostly applies to archaeological or art history respectively architectural types. 
One example would be chronological groups for certain archaeological material cultures. Enamelled disc brooches for example would be linked to a type "Carantanian C3" This type would have the timespan from 900 to 1000. 
Another example would be to link an E22 Sword to the type "Petersen X" that would have a timespan 900 to 1000.

This way objects (physical things E18 or E22) that do not have their own timespan defined can be traced chronologically via these chronological types.
#6

Updated by Stefan Eichert over 1 year ago

  • Assignee deleted (Stefan Eichert)
  • Description updated (diff)
#7

Updated by Stefan Eichert over 1 year ago

  • Description updated (diff)
#8

Updated by Alexander Watzinger over 1 year ago

  • Description updated (diff)
  • Subject changed from Timespans for types to Time spans for types

That they are only meant for custom types changes everything (maybe I missed it). In that case I think the suggestion for an option (default off) at creating/updating a custom type hierarchy would be most suitable. For now we could implement it like the multiple option: once set it cannot be removed. Hopefully a meeting will be possible soon so that we can discuss it shortly in person.

Thanks for the manual text proposal.

#9

Updated by Stefan Eichert 10 months ago

  • Description updated (diff)
#10

Updated by Alexander Watzinger 5 months ago

  • Target version changed from 6.0.0 to 6.2.0
#11

Updated by Stefan Eichert 4 months ago

  • Target version changed from 6.2.0 to 6.1.0
#12

Updated by Alexander Watzinger 4 months ago

  • Assignee set to Alexander Watzinger
  • Status changed from Acknowledged to Assigned
#13

Updated by Alexander Watzinger 4 months ago

  • Status changed from Assigned to Closed

I implemented types for dates and it will be released with 6.1.0.
Depending on how far we get with adapting API and Discovery for newest changes I may push the development version to THANADOS already this weekend and will send out newsletter if I do.

Also available in: Atom PDF