Difference between revisions of "Category:Historical Documents Working Group"
(→Example) |
(Add poll for time definition (chronology) related to historical documents) |
||
| Line 47: | Line 47: | ||
* a time | * a time | ||
| − | and contains a climate related data. (to be defined) | + | and contains a climate related data. (to be defined) |
| + | === Time === | ||
| + | The time derived for an event from historical documents is usually more precise than for other archive types. | ||
| + | Often the uncertainty is just days or even hours. So it would be best to code the absolute date by gregorian | ||
| + | calendar and a string of type ISO 8601. Optionally an absolute gregorian year (may be with floating point fraction | ||
| + | instead of integer) can be calculated as well. | ||
| − | (source_id,quote_id,license_event,doi_event,position_description,name_position,location_type,latitude,longitude,geometry,elevation,geonames_id | + | <poll> |
| + | How should the event time primarily be defined: | ||
| + | ISO 8601 mid-point time string and uncertainty in days (float) | ||
| + | Start and end time as ISO 8601 string | ||
| + | Gregorian year (float) | ||
| + | </poll> | ||
| + | |||
| + | The original sources often contain the information in calendar notation different than gregorian. | ||
| + | Julian calendar was used in Europe in historical time, but outside Europe other calendars existed | ||
| + | or still exist, likeweise in chinese or arabic documents. | ||
| + | |||
| + | <poll> | ||
| + | Should the time optionally be coded in other calendar systems: | ||
| + | yes | ||
| + | no | ||
| + | </poll> | ||
| + | |||
| + | If so, which parameters for start and end should be considered? | ||
| + | |||
| + | <poll> | ||
| + | Cycle: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | <poll> | ||
| + | Year: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | <poll> | ||
| + | Season / Solar Term: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | <poll> | ||
| + | Month: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | <poll> | ||
| + | Day: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | <poll> | ||
| + | Hour: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | It is also possible to extract the time related text from the quote and add it to a field 'phrase': | ||
| + | |||
| + | <poll> | ||
| + | Phrase: | ||
| + | Essential | ||
| + | Recommended | ||
| + | Desired | ||
| + | </poll> | ||
| + | |||
| + | |||
| + | (source_id,quote_id,license_event,doi_event,position_description,name_position,location_type,latitude,longitude,geometry,elevation,geonames_id,codeset_id,codeset_description,category,path,node_label,scale_label,scale_unit,value_label,value_index,average,variance,si_unit,si_average,si_variance | ||
) | ) | ||
Revision as of 08:06, 25 April 2019
Overview
In the Linked Earth context, a working group (WG) is a self-organized coalition of knowledgeable experts, whose activities are governed herewith. This page is dedicated to the discussion of data and metadata standards for historical documents, and aims to formulate a set of recommendations for such a standard.
Members of 'Historical Documents Working Group'
This working group contains only the following member.
Sources
Data is usually compiled from different historical sources. The LiPD data structure supports several Publication, that is normally used for referring to the publication describing the data. So this data cluster can be used for historical sources as well, in addition to the current publication describing the data.
Scans, Pages
Each source can optionally have a bunch of images, that are the scans of the pages inside the source. Maybe this can be dropped for the LiPD format and only references to external images should be added to the quotes.
Quotes
Out of each sources, several quotes could be extracted by transcribing them. Related data would most probably go into "measurementTables".
- Quote-ID: For later reference
- Reference to source: maybe short form like "Author()Year" is adequate
- Page: String of the page(s) number where the quote is extracted from
- Scan: Optional link(s) to externally stored image of this page(s)
- Language: The language of the quote (or it's translation)
- Protolanguage: The language the quote was written originally
- Quote: The quote itself (UTF8)
- License: License of the quote (cc)
- DOI: DOI, the quote is published
Events
Events, that are more like interpretations of the quote would go into "model part". Each events refers to
- a quote
- a position
- a time
and contains a climate related data. (to be defined)
Time
The time derived for an event from historical documents is usually more precise than for other archive types. Often the uncertainty is just days or even hours. So it would be best to code the absolute date by gregorian calendar and a string of type ISO 8601. Optionally an absolute gregorian year (may be with floating point fraction instead of integer) can be calculated as well.
You are not entitled to view results of this poll.
The original sources often contain the information in calendar notation different than gregorian. Julian calendar was used in Europe in historical time, but outside Europe other calendars existed or still exist, likeweise in chinese or arabic documents.
You are not entitled to view results of this poll.
If so, which parameters for start and end should be considered?
You are not entitled to view results of this poll.
You are not entitled to view results of this poll.
You are not entitled to view results of this poll.
You are not entitled to view results of this poll.
You are not entitled to view results of this poll.
You are not entitled to view results of this poll.
It is also possible to extract the time related text from the quote and add it to a field 'phrase':
You are not entitled to view results of this poll.
(source_id,quote_id,license_event,doi_event,position_description,name_position,location_type,latitude,longitude,geometry,elevation,geonames_id,codeset_id,codeset_description,category,path,node_label,scale_label,scale_unit,value_label,value_index,average,variance,si_unit,si_average,si_variance
)
Example
Rename LiPD file extension from zip to lpd
| Description | Tambora-Files | LiPD-Files | Remarks |
|---|---|---|---|
| Flood Example | Media:flood_tambora_csv.zip | Media:Exp0000.tambora.2017.zip | |
| To-Do | To-Do | To-Do | |
| To-Do | To-Do | To-Do |
Media in category "Historical Documents Working Group"
The following 6 files are in this category, out of 6 total.
