Forms/Objects Question(s)

[Audrey Sage]

Hi All, 

I am trying to figure out if there is a way to create a two-sided object with only one metadata file. Essentially, I am talking about a postcard. The issue I am running into is that in order to have a two-sided object, I need to create a compound object that is associated with two children. Creating the compound object is great, because that just gives me a little package in which to put my children objects. However, I cannot display my children objects without associating them with their own metadata files. This results in each of my compound objects having three different metadata files and forms: one for the compound object, one for the front of my postcard, and one for the back of my postcard. 

I was thinking of creating my own, custom form, but I don't think that will solve the problem. The real problem is that I don't seem to be able to display children within my compound objects that are metadata-less.

Am I missing something simple, or do I just have to work with all three of these metadata files? (The downfall of that is that all of the metadata is essentially the same, but does not sync, so edits to one form (e.g. a child's Large Object Form) do not show up in the compound object's metadata.) 

Thank you!

Best,

Audrey Lorberfeld

Digital Technical Specialist

The New York Academy of Medicine Library

[Amanda Lehman]

Hi Audrey,

I'm going to share some random thoughts since I don't have a solid answer.  

I have encountered similar situations where I create "stub" records for page objects of books that have a title and direction to the book or newspaper (parent) object for full metadata. But this doesn't solve your display aspect.  I agree that custom form work won't do you much good.  The easiest solution is of course a pdf.  Otherwise I might look into customizing the metadata display options for compound objects to have an option to always display parent metadata.  I've discussed this with our metadata librarian and he decided he was willing to describe the separate objects and treat the parent as a relational object instead of worrying about keeping everything synced up.  I have also resorted to the duplicate metadata records for many of our maps as that was the simplest way to deal with a large, complicated collection.  Maps: http://hdl.handle.net/10176/wyu:130121  Compound 

Alternately, you might be able to customize the compound object solution pack... I would see this situation as a use case for triggering a hook or action in your solution pack where if a child's Metadata is edited you can update the parent and vice versa so that all files are synced.  Ideally this situation will be solved when we move to purely RDF linked data style in Islandora CLAW

Again, my random thoughts, take as you wish and good luck to you!

[Audrey Sage]

Amanda,

Thank you for sharing your thoughts! Creating a 'stub' record is getting close to what we are going for, and your examples help us conceptualize our issue in a new too. We are gonna try to more experimentation on our end, but I will update this thread if we figure out a workable solution!

Best,

Audrey

[Audrey Sage]

Amanda,

When you make your compound objects display only the parent metadata, are you using the Display Parent Metadata utility module? https://github.com/mjordan/islandora_compound_parent_metadata.

Best,

Audrey

On Thursday, January 19, 2017 at 2:17:39 PM UTC-5, Amanda Lehman wrote:

[Amanda Lehman]

Audrey, nice find!! I've never used that module because we've finished our maps project before it was a thing - but I'll be using this in the future.  

Thanks to you and Mark Jordan! 

[Audrey Sage]

Amanda,

Interesting that you did not use that utility module! If you don't mind sharing, how did you make only the parent metadata show in compound objects then (like you did in your maps)?

Best,

Audrey

[Amanda Lehman]

Sorry for the confusion, we just duplicated the record across the parent and child objects. I plan to use this display option in the future when we have another such collection, or if we have a way to do a mass update of the maps during a migration.  

[Mark Jordan]

Amanda,

If you want to be able to display the parent metadata based on specific conditions such as PID namespace, child object content model, collection membership, etc., you may want to check out the Islandora Context module (https://github.com/mjordan/islandora_context), which duplicates the functionality of the Islandora Compound Parent Metadata module as a Context "reaction."

Mark

--
For more information about using this group, please read our Listserv Guidelines: http://islandora.ca/content/welcome-islandora-listserv
---
You received this message because you are subscribed to the Google Groups "islandora" group.
To unsubscribe from this group and stop receiving emails from it, send an email to islandora+...@googlegroups.com.
Visit this group at https://groups.google.com/group/islandora.
To view this discussion on the web visit https://groups.google.com/d/msgid/islandora/a415ffe0-c105-4a13-939b-68076dc90424%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Audrey Sage]

Amanda, I see. Thank you for the clarification! 

Mark, thank you for dropping in that information re: the Context Module. That looks really great.

Best,

Audrey