LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


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

CODE4LIB Home

CODE4LIB Home

CODE4LIB  March 2005

CODE4LIB March 2005

Subject:

Re: Authority Control for Databases

From:

"Binkley, Peter" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 4 Mar 2005 14:00:16 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (162 lines)

It would be good to base this on the data structure proposed in the
recent DLF Electronic Resource Management Initiative -
http://www.diglib.org/pubs/dlfermi0408/dlfermi0408appc.htm . An
Organization (vendor etc.) provides an Electronic Product, which
comprises at least one Interface and at least one E-Resource.
E-Resources can contain other E-Resources. So, how about
vendorID:interfaceID:resourceID. That would let you group dbs that share
an interface, simplifying the management of linking algorithms etc. In
fact, for linking purposes you might not need more than
interfaceID:resourceID. You only care about the vendor for licensing
purposes. The cases John mentions where a given resource may or may not
give access to a bunch of sub-resources (depending on your license)
could be addressed by refering to interfaceID:resourceID/subresourceID
(xpath-style) when you're specifying one of those subresources, and
interfaceID:resourceID(subresource1, subresource2, ...) when you're
specifying the packages you actually have. This could all be nicely
structured in XML.

The DLF recommendations are likely to become the model for new ERMS
products; I know that Ex Libris has brought the data structures in SFX
into line with this (adding an interface layer) in preparation for their
Verde ERMS product. So it's likely to be the model we'll all be using as
we all get standards-based ERMS's in the next few years.

The ids used in the SFX knowledge base would fill the bill, but it would
be good to have a non-proprietary set. How about starting with the CUFTS
database? http://www.theresearcher.ca/product_component_cufts.html

Peter

Peter Binkley
Digital Initiatives Technology Librarian
Information Technology Services
4-30 Cameron Library
University of Alberta Libraries
Edmonton, Alberta
Canada T6G 2J8
Phone: (780) 492-3743
Fax: (780) 492-9243
e-mail: [log in to unmask]



> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On
> Behalf Of Ross Singer
> Sent: Friday, March 04, 2005 12:57 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Authority Control for Databases
>
> John,
>
> This is a good question.  Of course, this isn't something
> that I figured could be solved in an afternoon (a Friday, at
> that!), but I think it warrants investigation.
>
> A way to address the situation you mention would be to add a
> 3rd field (maybe, I could be misunderstanding the problem) so:
>
> dbID:variantID:vendorID (or something)
>
> with variantID being a unique id to explain away the
> inconsistencies (:letters, :BCPapers, etc.)
>
> I don't really have a good answer in regards to "scope".  I
> think a definition of "database" would be in order.
>
> Maybe.
>
> -Ross.
>
> John Durno wrote:
>
> > I'd find something like this really useful for a couple of projects
> > I'm working on.
> >
> > I think the dbID:vendorID format could work quite well, as it
> > preserves both the fact that the content is the same and that it's
> > located in a different place. That's assuming that vendor
> here refers
> > to the host ... or does it refer to the publisher? Host would be
> > better I think, as there is generally only one publisher
> for a given
> > resource, but the host can often be any one of a number of service
> > providers. (eg. APA publishes PsycINFO ,which can be hosted
> by EBSCO,
> > ProQuest, OVID, etc.)
> >
> > There are complications arising from the fact that what
> constitutes a
> > "database" can be fairly fluid. eg. databases that consist
> of multiple
> > possible collections (thinking here of something like ProQuest's
> > Canadian Newsstand, which can be any or all of a number of regional
> > newspaper collections), or ebook databases like netLibrary.
> Not sure
> > how those kinds of content variations could be reflected in
> a standard
> > ID, or even if they should be.
> >
> > John
> >
> >
> > On 4-Mar-05, at 6:10 AM, Ross Singer wrote:
> >
> >> Thom,
> >>
> >> This is good news.  Whenever I think about this, I picture
> it looking
> >> something like a DOI:  like dbID:vendorID or something,
> but I don't
> >> know.  Do you have any details?
> >>
> >> Thanks,
> >> -Ross.
> >>
> >> Hickey,Thom wrote:
> >>
> >>> There's been some talk around here at OCLC about doing something
> >>> about this, especially to identify database-collections,
> which seem
> >>> to be entities people worry about too.
> >>>
> >>> --Th
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Code for Libraries
> [mailto:[log in to unmask]] On Behalf
> >>> Of Ross Singer
> >>> Sent: Friday, March 04, 2005 8:45 AM
> >>> To: [log in to unmask]
> >>> Subject: [CODE4LIB] Authority Control for Databases
> >>>
> >>> Is anybody aware of any type of standard identifier for
> databases?
> >>> Or any movement to create one?
> >>>
> >>> Matching on name seems very backwards.
> >>>
> >>> If there's not a group trying to create said authority, how could
> >>> something like that be started?  Would anybody else see
> value in this?
> >>>
> >>> Thanks,
> >>> -Ross.
> >>>
> >>>
> >>>
> >>
> >>
> > --
> > John Durno
> > Project Coordinator
> > BC Electronic Library Network
> > ~~~~~~~~~~~~~~~~~~~~
> > Phone: 604-268-7002
> > Fax: 604-291-3023
> > Email:   [log in to unmask]
> > Web: http://www.eln.bc.ca
> >
>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
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
January 2019
December 2018
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
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 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
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager