Dear all,
thanks for the replies.
On Shelley's point: I understand it is a specific kind of relationship
that we are trying to describe here, and that there are many possible
others that are in place among digital objects in a repository. The
point I wanted to raise here was that we believe none of the
relatedItem types available in MODS is capable of delivering the
proper semantics of the relationship between a scientific paper and
the data involved in the research activity that led to the
publication. And more and more we are facing this the issue of
representing this particular kind of relationship.
And this is also in reply to Rhonda: with the "isReferencedBy" and
"references" types we are not able to distinguish between other works
that are simply referenced in the publication and the dataset(s) a the
scientific results presented in a publication are based on. We wish to
be able to make this distinction vivid in some way.
In general I was not raising the general issue of relating any types
of items in a repository with other items (e.g. Shelley's example of
the text manual with the software program). Nevertheless I wish to
participate in a broader conversation about this more general topic. I
am sure there are other such use cases related to other digital object
types that have not been fully explored.
Looking forward to hear from you.
Best,
Simone
–––––––––––––
Simone Sacchi
Research and Scholarship Initiatives Manager
CDRS – Center for Digital Research and Scholarship
Columbia University
http://www.cdrs.columbia.edu
email: [log in to unmask]
phone: (212) 851-7339
On Tue, Apr 15, 2014 at 2:44 PM, Rhonda Marker <[log in to unmask]> wrote:
> Simone,
>
> I'd be interested to know why using the relatedItem types "isReferencedBy"
> and "references", along with typeOfResource and/or genre, is not applicable
> in this case. Otherwise, I tend to agree with Shelley that it might not be
> necessary to create a specific type of relationship for datasets associated
> with a publication.
>
> Rhonda
>
> ________________________________
> From: "Shelley Doljack" <[log in to unmask]>
> To: [log in to unmask]
> Sent: Tuesday, April 15, 2014 2:00:52 PM
>
> Subject: Re: [MODS] MODS relatedItem to associate datasets with research
> publications
>
> I think a relatedItem type specific to datasets is too narrow in scope for
> the types of material that may accompany a digital object being deposited in
> a repository. If a set of files for a computer program is the thing being
> deposited and it comes with a manual, could one use a relatedItem type to
> associate the text manual with the software program? Or is there another way
> to do this in MODS?
>
> Thanks,
> Shelley
>
> ----- Original Message -----
>> From: "Rebecca Guenther" <[log in to unmask]>
>> To: [log in to unmask]
>> Sent: Tuesday, April 15, 2014 7:49:01 AM
>> Subject: Re: [MODS] MODS relatedItem to associate datasets with research
>> publications
>>
>> The MODS Editorial Committee will consider this a proposal and discuss
>> adding
>> another type value to relatedItem. As you say, such a property is in
>> BIBFRAME.
>>
>> Rebecca
>>
>> Rebecca Squire Guenther
>> Library of Congress, Network Development and MARC Standards Office
>> Washington, DC
>> [log in to unmask]
>>
>>
>> -----Original Message-----
>> From: Metadata Object Description Schema List
>> [mailto:[log in to unmask]]
>> On Behalf Of Simone Sacchi
>> Sent: Thursday, April 10, 2014 5:49 PM
>> To: [log in to unmask]
>> Subject: [MODS] MODS relatedItem to associate datasets with research
>> publications
>>
>> Hello,
>>
>> We are using MODS as the metadata schema for our digital repository,
>> Academic
>> Commons. AC contains the scholarly work from Columbia faculty, students,
>> and staff of Columbia University. Increasingly, we are receiving data
>> files
>> along with the research publication (e.g. a conference paper). We would
>> like to describe these related files in a relatedItem section of the main
>> record, but none of the existing relatedItem types appears to fit this
>> case.
>>
>> The existing types are:
>>
>> "host"
>> "isReferencedBy"
>> "original"
>> "otherFormat"
>> "otherVersion"
>> "preceding"
>> "references"
>> "reviewOf"
>> "series"
>> "succeeding"
>>
>> Have other MODS users encountered this issue? If yes, how did you handle
>> it?
>> Would it be useful to introduce a new type to cover this situation?
>> MARC 21 includes the 786 (Data Source Entry) for "Information pertaining
>> to
>> a data source to which the described item is related. It may contain
>> information about other files, printed sources, or collection procedures".
>> There is also dataSource in BIBFRAME. Definition: "Has data source / Work
>> that is a data source to which the described resource is related.
>> It may contain information about other files, printed sources, or
>> collection
>> procedures."
>>
>> Looking forward to any suggestions / feedback.
>>
>> All the best,
>> Simone
>> -------------
>> Simone Sacchi
>> Research and Scholarship Initiatives Manager CDRS - Center for Digital
>> Research and Scholarship Columbia University http://www.cdrs.columbia.edu
>> email: [log in to unmask]
>> phone: (212) 851-7339
>>
>
>
> --
> Shelley Doljack
> Discovery Metadata Librarian
> Metadata Department
> Stanford University Libraries
> [log in to unmask]
> 650-725-0167
>
>
>
> --
> Rhonda J. Marker
> Head, Scholarly Communication Center
> Repository Collection Librarian
> Rutgers University Libraries
> http://rucore.libraries.rutgers.edu
> Phone: 848-932-5923
|