Hi Sophie,

It sounds like you are working on implementing complex objects in Islandora and you that all the issues and articles will be constituents in a complex object shell. Is that right?

And is the reason that you need the MODS records for the children so that you can have labels for the constituents?

I may be reading too much into your message, but if you are correct, we are struggling with a similar questions about how to implement complex objects in Islandora. We are not doing serial issues, but rather things like research articles with supplementary files, conference proceedings, and data sets.

Our material is a little different in that it is easy to assign a textual name to the component parts (something more than v.1, issue 1).

In our former implementation, we would not have created MODS records for the components, but would have used entries in the METS structMap to label the components.

We've come up with a couple ideas and would be happy to share them if that is what you are working on. We are probably far from coming up with the "right" answer, but will continue to work on it over the next few months.

Betsy

On Thu, Jul 17, 2014 at 3:53 PM, Sai Deng <[log in to unmask]> wrote:

Thanks Melanie,
We're actually cataloging serials, serial issues and serial analytical articles in a hierarchical structure. (The system we're using is Islandora. The MODs form for serials is locally created and is not part of the default Islandora installation. The development is still ongoing.)

We have a serial record as the parent MODS record, at the same time, under that parent record, we'll have issue level records (Child records). Now our question is:
For the issue MODS record, do we need to have the full information as presented in the serial parent record, or, it is enough to only have issue and number as shown in my previous email? For catalogers, we need to add the issue and number after finishing cataloging the parent record, and a program will generate the MODS records for the parent serial and the issues. So the question is: does the program need to get inherited information from the parent MODS? Is the MODs with only the following elements
<mods>< relatedItem><part><detail><caption>...</caption><number....</number></detail></part></relatedItem></mods>
Considered adequate?

We're still trying to decide how the analytical serial article MODs record should look like. We've seen LC's sample record, but our question is that:
If we have a parent MODs serial record, does the article MODs record still need to have the full information as presented in LC's site? How many elements would be necessary or preferred? What's the best practice here?

Thank you for any thoughts or suggestion!
Sophie

-----Original Message-----
From: Melanie Wacker [mailto:[log in to unmask]]
Sent: Thursday, July 17, 2014 3:34 PM
To: Metadata Object Description Schema List
Cc: Sai Deng
Subject: Re: [MODS] MODS coding for parent serial record, serial issues and analytical article level records

Dear Sophie,
could I ask you to clarify your question a bit? I am not quite sure what the main resource is that you are cataloging for your DAMS. Is the record for the serial, the issue, or are you cataloging specific articles?

There are some examples posted to the MODS Guidance page:
http://www.loc.gov/standards/mods/mods-guidance.html

Best,
Melanie

On 7/15/2014 1:34 PM, Sai Deng wrote:
> Hi dear list,
> In a DAMS repository, is it considered good practice to have a normal parent serial record and its issue records with only limited information (vol., no.), for example:
>
> <?xml version="1.0" encoding="UTF-8"?> <mods version="3.4"
> xsi:schemaLocation="http://www.loc.gov/mods/v3
> http://www.loc.gov/standards/mods/v3/mods-3-4.xsd"
> xmlns="http://www.loc.gov/mods/v3"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <relatedItem type="host">
> <part>
> <detail type="volume">
> <caption>Vol.</caption>
> <number>10</number>
> </detail>
> </part>
> </relatedItem></mods>
>
> Is the above MODS record considered adequate?
>
> What would you recommend for MODS coding for parent serial, serial issue records and article level records?
> Thank you for any feedback or suggestion!
>
> Sophie