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  February 2009

CODE4LIB February 2009

Subject:

Re: Duke metadata tool project

From:

David Kennedy <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 17 Feb 2009 16:37:06 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (144 lines)

Karen,

Thank you for your interest and comments.

To follow a little more on Will's response:

We also see components as being typed.  I think we just left this out of 
the system entities description.

We are using item type to aggregate tasks in the repository, determine the 
item's content model in the repository, what services should be exposed 
for the item, when the item is considered 'valid', etc.

Mixing media types within an item is doable.  And it may be best to add 
new item types as needed or extend existing item types to accomodate. 

I like your suggestion that an item could have more than one item type. 
This seems very elegant and object-oriented.  But it might also present 
some challenges in terms of aggregating tasks and determining when an item 
is valid and publishable.  I'll have to think this through some more.

As Will points out, we do have the same use case, with TEI and JPEGs.  And 
I don't know that we will know what solution works best for us until we 
get to the details.

Dave


-----
David Kennedy
Systems Programmer
Perkins Library, Duke University
(919) 613-6831
[log in to unmask]



Will Sexton <[log in to unmask]> 
Sent by: Code for Libraries <[log in to unmask]>
02/17/2009 04:16 PM
Please respond to
Code for Libraries <[log in to unmask]>


To
[log in to unmask]
cc

Subject
Re: [CODE4LIB] Duke metadata tool project






Karen, thanks for the feedback.  Is it ok if I opt for "eye of the 
beholder"? :)  We based our thinking for these models on the METS 
standard, where the component roughly corresponds to a file, and 
multiple configurations of files may exist for an item.  It does seem 
kind of strange that we might have an item, for example, something from 
our American Songsheets collection, which we call an "Image" type, but 
which has both JPEG's and TEI documents associated with it.  I wouldn't 
mind the English-usage misdemeanor as long as those files or components 
get successfully translated to services from the user's point of view: 
"View the image" | "Search the text".

We haven't been very specific about defining what our types are, and I 
don't know, but maybe the best response is, our typing won't be that 
strong.  Or at least, it should be extensible.  Anyway, I think you've 
identified one of those places where we'll be bargaining with the devil 
when we get to the details.

Will


Karen Coyle wrote:
> Thanks, Will. I took a look at some of this, and have some questions 
> about your system entities. You have both 'item' and 'component' 
> defined as:
>
> Item:
>  a discoverable unit in the digital repository.
>  An item contains 0 or more components.
>  If an item contains 1 or more components, it must also contain a 
> structural metadata record.
>  An item must contain one or more descriptive metadata records.
>  An item is typed; the item type determines what components are valid.
>  An item may have relationships with other items; ie. [item A] 
> isMemberOfCollection [item B]
>  An item will be assigned a status: Incomplete, Complete, Published, 
> etc.
> An item can be qualified with arbitrary indicators ("Needs 
> translation") that relate to the workflow of a
> given project.
>
> Component:
>  an atomic unit of digital content. For example, an image, a page of 
> a book, a text document, a pdf.
>  A component contains a bitstream representing the content, or a URI 
> pointing to a bitstream, as well as
> administrative metadata for the bitstream.
>
> This may need further explanation, as I am puzzled about the item 
> being typed, but the component not. It seems to be that definition of 
> 'item' and 'component' may be in the eye of the beholder, and that at 
> either level you would need to be clear about the digital type. It 
> also seems that many items will be of more than one type (text and 
> images being a prime example, but there is the whole 'kit' concept in 
> description cataloging.)
>
> If you'd like discussion to be on the blog, I can paste the question 
> into the comments area.
>
> kc
>
> Will Sexton wrote:
>> I posted here early in the winter on Duke's plans to develop a 
>> software tool to support metadata creation.  Our project has moved 
>> forward with the hiring of two programmers and an intensive phase of 
>> analysis and design.  We want to share our progress as we go, so I've 
>> composed a post with some of our design documents at
>>
>> 
http://library.duke.edu/blogs/digital-collections/2009/02/13/on-the-trident-project-part-1-architecture/ 

>>
>>
>> As always we welcome feedback from the code4lib community. 
>> Regrettably, we'll not send anyone to the conference next week, but I 
>> thought I would use this very nearly calm moment  to report on our 
>> progress and invite discussion.
>>
>> Best,
>>
>> Will
>> -- 
>> Will Sexton
>> Metadata Analyst / Programmer
>> Duke University Libraries
>>
>>
>
>

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

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