JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-LIBRARIES Archives


DC-LIBRARIES Archives

DC-LIBRARIES Archives


DC-LIBRARIES@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-LIBRARIES Home

DC-LIBRARIES Home

DC-LIBRARIES  April 2006

DC-LIBRARIES April 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: How to use Data.availabe to store start and end dates

From:

"Makarov, Vladimir/Medical Library" <[log in to unmask]>

Reply-To:

DC-Libraries Working Group <[log in to unmask]>

Date:

Thu, 27 Apr 2006 12:23:01 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Good Afternoon Andy et al,

We actually need it for digital collection. Therefore we need to store time period for for serials, date of edition for books (Date.dateCopyrighted) and creation date for images and other digitalized materials (Date.created). The users will see, for example:

 

Harrison's Internal Medicine, Copyright 2005 (for book)

 

The American journal of surgery (Closed end journal)

Coverage: Available from 1926 until 1994



Annals of surgery (Open end journal)

Coverage: Available from 1996 

 

We want to keep the system reasonably simple. I think that Andy is right, Date.available perhaps is not the best choice. How about using Coverage.temporal? 

 

Also, what exactly is Period? According to http://dublincore.org/documents/dcmi-period/

it can be used to refine Date or Coverage elements. But it is not a Qualifier. It is not a separate element either. 

 

Please forgive me if my question is too naive, but I am a new DC user,

 

Thanks a lot in advance,

Vlad

 

 

-----Original Message----- 

From: DC-Libraries Working Group on behalf of Andy Powell 

Sent: Thu 4/27/2006 11:34 AM 

To: [log in to unmask] 

Cc: 

Subject: Re: How to use Data.availabe to store start and end dates







	The collection-oriented approach suggested by John Robertson on

	dc-general makes sense to me.

	

	I also have some concerns that dcterms:available doesn't carry the right

	semantics for what you want.  For example, your holdings for a

	particular journal might run from 1998 until 2000, but the issues

	themselves might still be available (online or in the library) today.

	In that case, dcterms:available is an open-ended date range running from

	1998 to the current date.

	

	So I wonder if holding information is better modelled using a range of

	dates for dcterms:issued or for cld:dateContentsCreated (as per the

	collection description application profile)?

	

	Andy

	--

	Head of Development, Eduserv Foundation

	http://www.eduserv.org.uk/foundation/

	[log in to unmask]

	ჸ (0)1225 474319

	

	> -----Original Message-----

	> From: DC-Libraries Working Group

	> [mailto:[log in to unmask]] On Behalf Of Vladimir Makarov

	> Sent: 27 April 2006 04:41

	> To: [log in to unmask]

	> Subject: How to use Data.availabe to store start and end dates

	>

	> Dear Members,

	>

	> We are creating relational database (MySQL) to map DC

	> Metadata schema. We need to indicate the holding for some

	> journals. Holdings may be a range (ex. 1995 - 2005) when we

	> started and stopped subscription or, most often, the date

	> from resource became available till the present time.

	> According to the specifications at

	> http://dublincore.org/documents/2005/11/07/usageguide/qualifie

	> rs.shtml,

	>

	> the DC Element "Date" has following possible refinements (qualifiers)

	>

	> Created

	> Valid

	> Available

	> Issued

	> Modified

	> Date Accepted

	> Date Copyrighted

	> Date Submitted

	>

	> Available seems to be a good choice, as per

	> http://dublincore.org/documents/usageguide/qualifiers.shtml#available,

	> "Available" is a date (often a range) that the resource will

	> become or did become available.

	>

	> My question, however, is:

	> While entering the Date.available to MySQL table, we could

	> use the text column and enter it simply as "Available 1995 -

	> 2005" or "Available from

	> 1995 -- ", etc.

	> But I think everyone agrees that is not the best approach.

	> Date element should be represented by "Date" MySQL (or other

	> Database) column data type. We are tempted to add our own

	> qualifiers, such as "availableStart"

	> and "availableEnd", but wish to use standard qualifiers only

	> for interoperability reason.

	>

	> I am sure that the problem we are facing is not unique. If

	> someone is willing to share, we will greatly appreciate it,

	>

	> Many thanks in advance,

	>

	> Vlad

	>

	> ----------------------------------------------------------------

	> Vladimir Makarov

	> Memorial Sloan-Kettering Cancer Center Library

	> 1275 York Ave

	> New York, NY 10021

	> Tel: 212-639-7422

	> Fax: 212-717-3048

	> eMail: [log in to unmask]

	> ----------------------------------------------------------------

	>

	

	





 

     =====================================================================

     

     Please note that this e-mail and any files transmitted with it may be 

     privileged, confidential, and protected from disclosure under 

     applicable law. If the reader of this message is not the intended 

     recipient, or an employee or agent responsible for delivering this 

     message to the intended recipient, you are hereby notified that any 

     reading, dissemination, distribution, copying, or other use of this 

     communication or any of its attachments is strictly prohibited.  If 

     you have received this communication in error, please notify the 

     sender immediately by replying to this message and deleting this 

     message, any attachments, and all copies and backups from your 

     computer.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
July 2016
June 2016
May 2016
April 2016
March 2016
January 2016
December 2015
October 2015
June 2015
May 2015
March 2015
September 2014
July 2014
June 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
December 2012
November 2012
September 2012
August 2012
March 2012
February 2012
November 2011
October 2011
September 2011
July 2011
June 2011
January 2011
November 2010
October 2010
September 2010
August 2010
June 2010
May 2010
April 2010
March 2010
February 2010
October 2009
September 2009
June 2009
May 2009
March 2009
February 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
October 2007
September 2007
August 2007
July 2007
June 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
December 2005
November 2005
October 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
April 2004
March 2004
February 2004
December 2003
November 2003
October 2003
September 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
November 2002
October 2002
September 2002
July 2002
May 2002
April 2002
March 2002
January 2002
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
July 2000
June 2000
April 2000
March 2000
February 2000
January 2000
December 1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager