[DDI-ADG] time pieces in V 2.0

Mon Jul 25 14:14:08 EDT 2005

Hi.

Just one remark - I think multiple ranges could be specified in Version 
2.0, by using the attribute "cycle". For example,

<timePrd event="start" date="1998-05-01" cycle="1" (or:"Wave 1", or "Cycle 
1")>May 1, 1998</timePrd>
<timePrd event="end" "date="1998-05-31" cycle="1" (or:"Wave 1", or "Cycle 
1")>May 31, 1998</timePrd>,

then,

<timePrd event="start" date="2000-05-01" cycle="2" (or:"Wave 2", or "Cycle 
2")>May 1, 1998</timePrd>
<timePrd event="end" "date="2000-05-25" cycle="2" (or:"Wave 2", or "Cycle 
2")>May 25, 1998</timePrd>,

the difficulty was that we did not have a controlled vocabulary for the 
"cycle" attribute, so it was hard to read by software.

Sanda.

At 01:42 PM 7/25/2005, Mary Vardigan wrote:
>Thanks, Sanda. A few questions/comments:
>
>* A goal for Version 3.0 is to have a way to specify multiple date ranges 
>in Time Period and Date of Collection. This wasn't possible in Version 
>2.0. Plus we might want to associate the date ranges with cycles.
>
>* Does it make sense to have Time Method as a discrete methodology item or 
>should this be broader to encompass other types of methodologies? Either 
>way, do we want a controlled vocabulary for this? If so, how do we develop 
>it? Ken has done some of this work in compiling the different types of 
>methodologies for ELSST.
>
>* Re frequency, this could describe a dataset or a data series. Should it 
>be an element associated with Series information also?
>
>* We might also discuss the issues of administrative dates and what our 
>responsibility is in that area.
>
>Mary
>
>At 08:48 AM 7/21/2005, Sanda Ionescu wrote:
>>Section 2, Study Description:
>>
>>2.2.3.1 <timePrd event="" date="" cycle="">
>>
>>Tag Library description and examples:
>>Description: The time period to which the data refer. This item reflects 
>>the time period covered by the data, not the dates of coding or making 
>>documents machine-readable or the dates the data were collected. Also 
>>known as span. Use the event attribute to specify "start", "end", or 
>>"single" for each date entered. The ISO standard for dates (YYYY-MM-DD) 
>>is recommended for use with the "date" attribute. The "cycle" attribute 
>>permits specification of the relevant cycle, wave, or round of data. Maps 
>>to Dublin Core Coverage element. Inclusion of this element is recommended.
>>
>>Example(s):
>><timePrd event="start" date="1998-05-01">May 1, 1998</timePrd>
>><timePrd event="end" "date=1998-05-31">May 31, 1998</timePrd>
>>
>>2.2.3.2 <collDate event="" date="" cycle="">
>>
>>Description: Contains the date(s) when the data were collected. Use the 
>>event attribute to specify "start", "end", or "single" for each date 
>>entered. The ISO standard for dates (YYYY-MM-DD) is recommended for use 
>>with the "date" attribute. The "cycle" attribute permits specification of 
>>the relevant cycle, wave, or round of data. Maps to Dublin Core Coverage 
>>element. Inclusion of this element in the codebook is recommended.
>>
>>Example(s):
>><collDate event="single" date="1998-11-10">10 November 1998</collDate>
>>
>>
>>2.3.1.1 <timeMeth method="">
>>
>>Description: The time method or time dimension of the data collection. 
>>The "method" attribute is included to permit the development of a 
>>controlled vocabulary for this element.
>>
>>Example(s):
>><timeMeth>panel survey</timeMeth>
>><timeMeth>cross-section</timeMeth>
>><timeMeth>trend study</timeMeth>
>><timeMeth>time-series</timeMeth>
>>
>>2.3.1.3 <frequenc freq="">
>>
>>Description: For data collected at more than one point in time, the 
>>frequency with which the data were collected. The "freq" attribute is 
>>included to permit the development of a controlled vocabulary for this element.
>>
>>Example(s):
>><freq>monthly</freq>
>><freq>quarterly</freq>
>>
>>4.3 <var temporal="">
>>
>>The attribute "temporal" indicates whether the variable relays 
>>time-related information. (Currently set as Y|N with N as a default).
>>
>>[Aside from these, of course,  we have the various dates in citation, but 
>>those are "administrative" rather than study-related information].
>>
>>Sanda.
>>
>>
>>
>>
>>Sanda Ionescu,
>>Research Associate
>>Inter-university Consortium for Political and Social Research (ICPSR)
>>The University of Michigan
>>P.O. Box 1248
>>Ann Arbor, MI 48106
>>
>>Phone: (734) 615-7890
>>Fax: (734) 615-7890
>>        (734) 647-8200
>>
>>_______________________________________________
>>DDI-ADG mailing list
>>DDI-ADG at icpsr.umich.edu
>>http://www.icpsr.umich.edu/mailman/listinfo/ddi-adg
>
>Mary Vardigan
>Director, Collection Delivery
>Inter-university Consortium for Political and Social Research (ICPSR)
>University of Michigan
>P.O. Box 1248, Ann Arbor, MI 48106-1248
>Phone: 734-615-7908
>Fax: 734-647-8200
>www.icpsr.umich.edu

Sanda Ionescu,
Research Associate
Inter-university Consortium for Political and Social Research (ICPSR)
The University of Michigan
P.O. Box 1248
Ann Arbor, MI 48106

Phone: (734) 615-7890
Fax: (734) 615-7890
        (734) 647-8200