search

MetadataDeluxe / VRA-Core-Essentials-ExifTool-config

MIT License
2 stars 2 forks source link

VRA Preset for jExifTolGUI #1

Open mrtngrsbch opened 3 years ago

mrtngrsbch commented 3 years ago

Hi,

I just created the VRAE preset for jExifToolGUI. At the moment I can't get to edit the data and I hope to solve it soon.

jExifToolGUI-vrae_view jExifToolGUI-vrae_Preset

MetadataDeluxe commented 3 years ago

I had trouble editing with the ExifTool command line because of the period (".") in the vrae tags, e.g., 'work.agent'. I had to define an ExifTool-friendly tag name, e.g., Name => 'WorkAgent'. Perhaps this is causing a problem in jExifToolGUI.

MetadataDeluxe commented 3 years ago

I posted about the editing problem on the ExifTool Forum https://exiftool.org/forum/index.php?topic=12358.0 I just saw that Phil Harvey will consider adding VRA to ExifTool. That would be great!

mrtngrsbch commented 3 years ago

I had trouble editing with the ExifTool command line because of the period (".") in the vrae tags, e.g., 'work.agent'. I had to define an ExifTool-friendly tag name, e.g., Name => 'WorkAgent'. Perhaps this is causing a problem in jExifToolGUI.

humm... possibly, but I can't say for sure. Right now I'm a bit lost in my documentation that gets chaotic. And speaking of which: some time ago I saw that you had posted [VRAE_ExifTool_Tags.xlsx] on Google Drive: https://docs.google.com/spreadsheets/d/1Dqft1ZKvyE-Hjxesl1Fh1xI1I-CMoHYxlfjxI5JWc_g/edit?hl=en&hl=en#gid=2

Trying to make a merge with my documentation: https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit?usp=sharing

MetadataDeluxe commented 3 years ago

This is very exciting! I am happy to help. Also, I am willing to change my spreadsheet and documentation to work better, if you have any ideas.

mrtngrsbch commented 3 years ago

ideas... humm... what do you think of these ideas?

  1. [You] Unify VRA documentation: merge [https://docs.google.com/spreadsheets/d/1Dqft1ZKvyE-Hjxesl1Fh1xI1I-CMoHYxlfjxI5JWc_g/edit?hl=en&hl=en#gid=2] + [https://github.com/MetadataDeluxe/VRA-Core-Essentials-ExifTool-config/blob/main/Documentation/VRAE_ExifTool_Tags.xlsx].
  2. [You] Impact in repository
  3. [You] Change permissions to accept comments and/or accept contributors
  4. [Me] Delete my Vra Core 4 template [https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547]
  5. [Me] Create a Google Sheets script to integrate [https://docs.google.com/spreadsheets/d/1Dqft1ZKvyE-Hjxesl1Fh1xI1I-CMoHYxlfjxI5JWc_g/edit?hl=en&hl=en#gid=2] to my spreadsheet [https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547].
MetadataDeluxe commented 3 years ago

[You] Change permissions to accept comments and/or accept contributors - yes, I will do this (I just forgot before).

The problem is that the other VRA documentation I have was created specifically for the VRA Bridge tools and related tools VRA Core Tools. They were intended to work together and have the same set of selected VRA fields and limitations. For example, In true VRA Core, you can repeat Work Subject as many times as you want. In the VRA Tools we limited them to Work_Subject1, Work_Subject3, Work_Subject3 in order to create a consistent spreadsheet export-import template. We had to guess at how many repeating items users would need, which is a compromise (and perhaps wrong).

On Mega_EM_Crosswalk - tab VCatCore4, the name "VCat" refers to a Filemaker Pro database created by a VRA member.

I am not sure about merging that with VRAE_ExifTool_Tags.xlsx I was thinking of ExifTool VRA as more versatile, with full structured arrays that will allow as many repetitions as needed. This will create an incompatibility with the older VRA Tools, unless the user is careful to match the old spec. I was conflicted about this - should I make ExifTool only to match the old VRA Tools, or let users decide to use VRA in other environments? I was thinking I would inform users which ExifTool VRA tags match the VRA Bridge Tools, but I have not specified how to match fields like Work_Subject1, Work_Subject3, Work_Subject3 - I only specified that WorkSubjectIndexed is included in Bridge. I can add this, if it is helpful. Maybe that is what you are suggesting - specify how to read-write VRA Bridge metadata using ExifTool?

mrtngrsbch commented 3 years ago

A. I understand that you have an inheritance of commitments. If it's okay with you and if you can handle it on your end, I might recommend that you keep [VRAE_ExifTool_Tags.xlsx ], but the one who really knows about it is you. Handle it as you think best.

Regarding the limitation of 'Work Project' as well as 'Custom Field', I think we are facing man-machine limitations. I think it would be important to write a README/HOWTO/DISCLAIMER with these clarifications and limitations. E.g.: 'Work_Subject' can be infinite, but in this implementation we have limited it to 2-3 elements. If you have the need to use more fields, you can create them in the 'vrae.cfg' file and later in your custom preset. You can also write to the workgroup to be notified of the need. But (personally) I think that 3 fields is not enough. The only annoyance I see is when editing XLS files with many columns.

B. Now that you say that, I think again and I think it is wiser to keep the documents separate.

Q:"I was conflicted about this - should I make ExifTool only to match the old VRA Tools, or let users decide to use VRA in other environments?"

I really don't know what to tell you. Personally I think that if the above tools belong to another branch, then we should not import the problem to ExifTool. But maybe my approach is very selfish, as I really don't know their use and user community.

Q:"Maybe that is what you are suggesting - specify how to read-write VRA Bridge metadata using ExifTool?" I was really thinking about how to fully document the whole implementation inside ExifTool/jExifToolGUI. Therefore, in my sheet [https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=0] I make an unambiguous reference to the standard. That is to say that it is not only an internal technical document, but also accessible to all audiences and with verified references.

Well, I hope I have expressed myself correctly. Don't hesitate to ask me about those dark corners.

Off Topic: Regarding a previous comment you had told me about the quality of jExifToolGUI: A: Including ISAD(G) and VRAE to ExifTool I think is undoubtedly the right and best way to go. B: It is true that jExifToolGUI needs a lot of improvements and many of them we know. I would say that the main drawback is the resources we have, because we don't do this in a dedicated way and we don't have a budget. Undoubtedly this would be easier with some financial help. In my case I have managed to get a very small budget that I got from a contest, although it will not be enough, for now. [https://docs.museosabiertos.org/editor-de-metadatos]

mrtngrsbch commented 3 years ago

Hi monday, @MetadataDeluxe

I have made progress with the jExifToolGUI preset and I just need to add the 6 custom fields [CUSTOM 1-6 LABEL]. Unfortunately there is no way to export it yet, but I think the issue is created. I have also improved my documentation to reflect this Mix Schema as well as possible.
[https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547]

Please let me know if you have an idea to improve it.

image

image

MetadataDeluxe commented 3 years ago

Thanks for your comments @mrtngrsbch , this is helpful.

A. I agree that I will keep [VRAE_ExifTool_Tags.xlsx ] and edit it as VRA-Core-Essentials-ExifTool-config improves with use. As we have discussed before, I don't know what will happen with the VRA Bridge Tools, although (to my surprise) I recently received a request to convert the Bridge Tools to española, so maybe there is more interest than I thought. I just wish Bridge were more reliable.

Thanks for the suggested README/HOWTO/DISCLAIMER. I will add that.

I agree that "we should not import the problem to ExifTool". ExifTool should be a more open and complete expression, although VRAE is still selective about VRA elements. This is because a 100% expression of all VRA Core elements and global attributes would be at over1,000 tags and many might never be used in an XMP environment. I think we can add elements/attributes, if people request them. In other words, VRA-Core-Essentials-ExifTool-config can grow as needed for the real world.

About "how to fully document the whole implementation inside ExifTool/jExifToolGUI" - yes, this is a challenge. ExifTool documentation uses flattened tag names for array structures, e.g., iptcExt ArtworkOrObjectAOCreator . I find that a little confusing, especially if there are multiple array items. I'm still trying to think of a better way to express structured array tags. I don't know how to cleanly express a command like this is in a vertical spreadsheet column: -xmp-vrae:WorkMaterialIndexed="[{value=bronze, vocab=AAT, refid=300010957, href=http://vocab.getty.edu/aat/300010957}, {value=marble, vocab=AAT, refid=300011443, href=http://vocab.getty.edu/aat/300011443, extent=base}]"

Let me think about this.

Congratulation on your progress with jExifToolGUI preset for VRAE! Give me some time to look at [https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547] and think about suggestions.

About improvements to jExifToolGUI: It is a big task to undertake! I have some thoughts on small steps to take. Should I post those to jExifToolGUI on GitHub so others can discuss?

mrtngrsbch commented 3 years ago

Por favor, lea mis comentarios como sugerencias, ideas, deseos y también interrogantes.

A. Keep [VRAE_ExifTool_Tags.xlsx] = OK

Regarding the Spanish version... (I am responsible for jExifToolGUI Spanish translation & manual) = I have several things to say about it:

  1. When you say Bridge Tools, do you mean VRA Metadata Palette?

  2. Before making the ES version it is more 'much' more important to get a 'time stable version'. (My version of 2020-1-23 for OSX is still unstable. For example, after two clicks the window closes). note: VRA Metadata Palette is awesome and a great job for writing metadata. The only problem I find is the underlying technology and the dependency on its evolution and licensing.

  3. An ES version does not guarantee that Spanish-speaking users will use it (my case) because the metadata universe is very complex and adding terminology in another language can help... but it can also complicate. For example: that would imply that you plan to use the AAT thesaurus in Spanish? [https://www.aatespanol.cl/]

For these and other considerations (open source, multiplatform, java, compatibility with servers thanks to the fact that ExifTool is installed almost by default in Linux *) is that my idea (my dream, my desires) is that I decided to rely on ExifTool/jExifToolGUI, in order to create presets for VRAE, ISAD(G), DC, EAD, etc ....

Indeed, I know and adhere to the embedded data manifest [http://www.embeddedmetadata.org/], which should never be deleted ;-)

Therefore, my workflow project is:

  1. Edit the image metadata on the desktop.
  2. Upload the image
  3. The CMS displays the metadata in the page content.
  4. [in the future] Create a SPARQL Endpoint to query the data

Also - in the future - an interface that can accommodate +1000 tags could be created. It is just developing the appropriate tool to create the necessary fields. Let's not forget that VRAE is an extensible XML and we are now learning to struggle with tabular structured data.

With regard to implementing -xmp-vrae:WorkMaterialIndexed="[{value=bronze, vocab=AAT, refid=300010957, href= http://vocab.getty.edu/aat/300010957 }, {value=marble, vocab=AAT, refid=300011443, href= http://vocab.getty.edu/aat/300011443 , extent=base}] My opinion is to ask Phil how to do it in the best possible way and always be compatible with ExifTool. It's just a bit of patience, but possible. This kind of nested data should be solved in jExifToolGUI by creating a special panel. That is my conclusion and it requires an ad hoc development. This point is an important milestone since jExifToolGUI was not created for these issues and Harry does not have this problem as a priority = it is up to us to develop this particularity and I hope to be able to start it this year.

About improvements to jExifToolGUI: Yes, I think your comments would be very important and welcome. Please, include in the project everything you think is important.

MetadataDeluxe commented 3 years ago

Regarding the Spanish version of the VRA Tools... yes, the VRA Metadata Palette and the Export-Import Tool. The palette would require a lot of work - lots of translation and lots of script changes. Good point about AAT thesaurus. Yes, I think it would have to be in Spanish. Search, display, and embedding would be possible, but perhaps you are right that it would not be used much and would just create new complications. Of course, Bridge 2021 has a bug so the Getty search no longer works! Unless they fix that, there is no reason to use it.

I was not planning on doing any more development on the palette except for bugs reported by users. I have recently received feedback from a few people who are using so, I now am not sure - still thinking about it and looking at alternatives. By the way, I have fixed a couple of bugs and I think the current version (2021-04-18) is stable link.

I agree that ExifTool is the preferred XMP backend to use. Certainly most developers use it. In addition to you, another person recently asked me if there is a VRA ExifTool config and justified it with the same arguments you used.

I like your suggested workflow. How will a user re-submit metadata if they change it (edits, improvements, etc.)?

mrtngrsbch commented 3 years ago

Indeed, Spanish translation is a more complex task than imagined because there are many regionalisms. In the early days of Drupal we wisely opted to use a neutral Castilian (Spanish), but even so, it is necessary to get consensus for technical terminology. Of course, you can count on my support for whatever you think I can do to help ! Bridge 2021 has a bug? another bug? Personally I have no problems with commercial applications, but I'm not habituated to not having visibility of the project and that issue stresses me a lot.

Personally (also not an advice) I would not move forward with the translation until I know how many people use it and have feedback. 20 users? 1000 users? As I wrote above: I often use the English version because the translations can be more confusing and have less search results when one needs to learn or document.

Undoubtedly the preferred backend is ExifTool and it is very important that the technical community supports it because we are the ones who do the monitoring and maintenance of user tools and we know the ins and outs of it.

MetadataDeluxe commented 3 years ago

About https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547

The VRAE custom properties are intended to be used with both _label and data custom1/vrae:_label custom1/vrae:data

_label allows the user to assign a meaningful label - basically defining the use of the data.

 <vrae:custom1 rdf:parseType="Resource">
    <vrae:_label>Greg's Inventory Number</vrae:_label>
    <vrae:data>TI: 92677432</vrae:data>
 </vrae:custom1>
mrtngrsbch commented 3 years ago

Hi @MetadataDeluxe ,

Thank you very much for your clarification. For the moment I have included your note to each field. Unfortunately the jExifToolGUI presets do not allow (for the moment) to edit the label as VRAE tries.

This can probably happen with a future implementation that we can study.

MetadataDeluxe commented 3 years ago

@mrtngrsbch I have updated the documentation spreadsheet: https://github.com/MetadataDeluxe/VRA-Core-Essentials-ExifTool-config/blob/main/Documentation/VRAE_ExifTool_Tags.xlsx

I made some changes to match the typical ExifTool documentation:

Does this give you any ideas for your GLAM spreadsheet [https://docs.google.com/spreadsheets/d/1lgJ7bgF3YWYn6RpQe6xPpc2lPtMmsKxhdoTDaipEz4M/edit#gid=553123547] ?

I can post this to the ExifTool forum to see if Phil, or anyone else, has any other ideas to clearly document structured fields. I am imagining myself as someone who sees vrae for the first time and wants to quickly understand how to use it in ExifTool. How d oI construct a read or write command?

mrtngrsbch commented 3 years ago

Hi @MetadataDeluxe,

wow, excellent work ! Sorry I had lost this message.

I think it is excellent to share this work in the ExifTool forum. There is always someone who has new or different ideas that can collaborate with the project.

I'm currently busy with a project, but when I'm done I'll be able to check my spreadsheet with calm.

best

mrtngrsbch commented 3 years ago

@MetadataDeluxe, I liked the addition of ExifTool to the table.

image

MetadataDeluxe commented 3 years ago

Thanks @mrtngrsbch

I did share the question on the ExifTool forum, but replies yet. https://exiftool.org/forum/index.php?topic=12358.0