Question about media metadata bulkloader relationships

[campmlc]

Quick question - in the media metadata bulkloader column "media relationships" = associated with project, what do we put for the value for media_related_term_1? The project url or just the project number embedded in the url, or ?

[dustymc]

10000356

[campmlc]

We should add that to the documentation, which currently only has:

Documentation for code table MEDIA_RELATIONSHIP ~ [ table list ]  

Manage Metadata

MEDIA_RELATIONSHIP | Documentation | Metadata -- | -- | -- associated with project [ link ] | Media with an association to projects, but one which cannot be expressed more directly, e.g., through involved specimens.

[campmlc]

Also need to add to documentation here: https://handbook.arctosdb.org/how_to/How-to-Bulkload-Media-Metadata.html

[dustymc]

The code table documentation describes the form and intent of relationships between data objects. The bulkloader documentation describes how to reference data objects for a very specific purpose. Those are different things, and I don't think anything is missing.

How-tos are yet another thing - they're examples of how to use stuff, not strictly "documentation." There are lots of ways to create media relationships, one of them involves a particular bulkloader, the how-to is an overview of some of the ways to use the tools.

[campmlc]

I am trying to follow the how-tos to create a media metadata file, and it is missing critical informaton that is only found on the media metadata bulkload load csv page. It would be exceedingly helpful if all the instructions for doing this complex process were in one place- or in multiple places, so we don't have to toggle between so many forms and code tables and bulkloaders just to fill in values in a spreadsheet.

[campmlc]

Another question on using media labels - can barcode be used for other containers besides herbarium sheets? If I add a container barcode as a media label, does that break anything? I have images taken from barcoded slides.

[campmlc]

And am I allowed to add more than one label per label type? E.g. more than one media_label and media_label_value for description?

[Jegelewicz]

@campmlc Please just write the needed documentation. We don't have anyone dedicated to do this and it never gets properly done because nobody takes the time to do it. PLEASE either write down what you think needs added here so that I can add it or just add it yourself. We have way too many issues asking for documentation to be changed or written and nobody following up.

[campmlc]

I can't stop in the middle of what I am trying to do to write the documentation, unfortunately - which is why I was posting here. I'll try to remember to come back to it, but I am deep in the weeds of learning a new and confusing process.

[campmlc]

See also #4193 - I can't check to see what others have used for media label value because the search tool is not working.

[dustymc]

instructions for doing this complex process were in one place

I don't really disagree, but I don't think we can realistically expect to maintain that either. I don't want to have to update the bulkloader when a term definition changes, and I don't want to have to update the 37 how-tos when the bulkloader changes. I can get by part of that by pulling/linking bits of Arctos (eg the CT documentation) into other bits (eg bulkloaders), but that doesn't extend to the how-tos (in the current architecture). Lacking a documentation team, I think this really has to be seen as three things:

• how the data/model/guts/core-bits actually work (eg code tables)
• how tools work (usually-inline documentation)
• how someone's used some tool to accomplish some task (how-tos).

Barcode is just text; you can do whatever you want with it, as long as that can be done in UTF. It's really handy for processing images, I'd not recommend denormalizing if you're attaching images to some sort of container-related record. There's no relationship between the Arctos container model and media label "barcode."

You can apply any number of media labels, but duplicates can break things like multi-page documents and title/alt tags. Duplicating description will lead to something weird in the UI.

[campmlc]

This sounds like a great idea: pulling/linking bits of Arctos (eg the CT documentation) into other bits (eg bulkloaders)

[dustymc]

great idea:

I agree; that's why I've been doing it forever!

Some other format is possible; that would need discussed separately and could be incorporated as the next component loader version.

[campmlc]

And if we had the information on what value to use for e.g. the project label in the associated CT, then all would be in one place . . .

[dustymc]

had the information on what value to use for e.g. the project label in the associated CT, then all would be in one place .

That would just be wrong. The relationship - what's described in the code table - is to the data object, not any summary, url-bit, identifier, or any other subset or representation of the data object. (And what "the data object" consists of depends entirely on your viewpoint; there are no hard lines.)

[campmlc]

I don't think we are communicating well - I'm not talking about putting a specific data object in the code table.