Hi all,
I’m currently evaluating Omeka S for a new project, which is a software library, cataloguing optical media to be precise.
For example, I have Software A that spans across Disc Y and Z. I keep both Discs as separate items and add them to an Item group which makes up Software A.
Now, here’s the problem. Each Disc can consist of multiple tracks. I need to store multiple values per Track: Number, size, checksum and so on. The important part is that the properties of a given track must be “unique”, so I have to make sure that a linked checksum is only added for the track with a specific number.
Adding the track properties (let’s call them trackNum, trackSize, trackChecksum) multiple times to an item would lead to inconsistencies, so I would loose the connection that trackNum of the item is always the same trackChecksum, correct?
If so, which is the best approach to solve this?
I’m almost tempted to create a new item per Track and link the “track items” to the disc item which then will be linked to the software item.
Any ideas or recommendations?
Now that I think about it - adding the tracks themselves as items wouldn’t be the worst idea, because theoretically, a track with a certain size (and this checksum) can be present on multiple discs.
But I’m not entirely sure if this would be conceptually wrong.
I think you’re right that adding the tracks as items is the optimal approach. It’s conceptually correct and allows the maximum level of semantic possibilities. Look into using the “Ontology for Media Resources” vocabulary for describing your media. It provides (on top of many other things) a :hasTrack property and :Track class, so you can unambiguously link your media resources to their component tracks.
Thank you, this sounds really promising! Thank you very much for pointing out the additional vocabulary, I was about to create it entirely from scratch…
Now I need to finalize my understanding of how the different properties work together 
Hi all, currently playing around with it and I really like the concept of adding each track of a disc as seperate item, this will allow for incredible flexibility using the advanced metadata search.
However, I currently run into a display issue, and the problem is that I’m not sure what I am even searching for.
I have the following disc entry:
The track has the following properties:
I think both resources are linked properly because they “know” eachother.
However, is there a way to show all properties of all resources in the “Items with…” tables, so I see everything at a glance?
Thank you!
I think I solved it - I edited application/view/common/linked-resources.phtml and modified the table to access the different item values like that:
<td>
<?php if ($value['val']->resource()->value('dcterms:publisher')): ?>
<span class="resource-class"><?php echo $this->escapeHtml($this->translate($value['val']->resource()->value('dcterms:publisher'))); ?></span>
<?php endif; ?>
</td>
@felsqualle I just wanted to add, in case you don’t know already, that you don’t want to edit the files in the /application folder because they will be overridden when you upgrade Omeka.
You’ll want to copy the file into your theme and edit the copied version. You can read more about this process here: Theme Modifications - Omeka S Developer Documentation
@fackrellj Thank you, that’s really helpful!
I discovered that I need to modify at least one other file (I need to print the output of some specific values in <pre> flags, so I have to adapt the script that provides the output to add the tags if it finds the values I specify).
So I think the best way would be to basically fork the “Foundation” theme I am using and then put the modified files there, then I have everything update-safe.
Thanks again for your help all!
