Project

General

Profile

Feature #1748

Updated by Stefan Eichert almost 2 years ago

In order to manage types, that require certain additional information I propose the following: 

 Idea: For e.g. radiocarbon data we need certain values that define the relation between an entity and the respective Type: 
 E18 physical thing (Wooden bucket) - P2 has type - Radiocarbon dating. The link itself has another property - P3 has note - E62 String 
 So we can document "Wooden bucket" - {"lab id": "VERA", "sample id": "VERA1234", "14C Years": 1200, "range": "30"} - Radiocarbon dating 

 This would apply to various cases. E.g. if you have certain measurements with a range like 500 +- 30, Or if you need to document the measuring device, its error or a certain method. 

 I suggest to define a new openatlas_class type to accomplish that. 

 When creating a new type like this (only doable by admins), the user defines a number of fields and their attributes: label + type of values (string, integer, float) 
 The user interface validates them when entered and displays them with the respective labels. 

 The information could be stored in the description field of the link. E.g. as JSON: {"label1": "string", "label 2": "string", "label 3": INT, "label 4": float} 

Back