Difference between revisions of "Category:Historical Documents Working Group"

From Linked Earth Wiki
Jump to: navigation, search
( Pages with a poll, 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,calendar,begin_year,begin_month,begin_day,begin_hour,begin_timestamp,end_year,end_month,end_day,end_hour,end_timestamp,codeset_id,codeset_description,category,path,node_label,scale_label,scale_unit,value_label,value_index,average,variance,si_unit,si_average,si_variance
+
<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 01: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.

How should the event time primarily be defined:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 00:48, 25 April 2019.
poll-id F5072947F0CB8D3862347216F0EFEB01

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.

Should the time optionally be coded in other calendar systems:
You are not entitled to vote.
You are not entitled to view results of this poll.
There were 0 votes since the poll was created on 00:52, 25 April 2019.
poll-id 6C4C91C54F190A35F0495EFC579ABBAD

If so, which parameters for start and end should be considered?

Cycle:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 00:59, 25 April 2019.
poll-id 6E47C6143936C80F76DA4595BBF0D6ED

Year:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 00:55, 25 April 2019.
poll-id 0EB04C5BBFD4BFC1FC4B11060C545D4B

Season / Solar Term:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 01:00, 25 April 2019.
poll-id 410789FBAD74B0772DE299546EC469DF

Month:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 00:55, 25 April 2019.
poll-id 03120082E79709CF299C7126AF4C3039

Day:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 00:55, 25 April 2019.
poll-id B6DDAAF86768F314B8E23B0F1C574BBF

Hour:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 01:00, 25 April 2019.
poll-id 4B6DF41D3FB86CC1DD016AA7C316FAD8

It is also possible to extract the time related text from the quote and add it to a field 'phrase':

Phrase:
You are not entitled to vote.
You are not entitled to view results of this poll.
There was one vote since the poll was created on 01:05, 25 April 2019.
poll-id E522F65760245A919C128E17FB915D93


(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 )

https://sweet.jpl.nasa.gov/

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.