Why are the higher-level fields not written?

Post Reply
Bongo
Posts: 46
Joined: 22 Mar 10 19:11
Location: Ingolstadt, Germany
Contact:

Why are the higher-level fields not written?

Post by Bongo » 24 Feb 21 17:57

I've built a new structure for Darwin Core. Each label is mapping to a field. For example dwc: Taxon.dwc: kingdom. When I save the metadata, the entire hierarchy is written in the keywords. But the Dawin Core fields are not written.

I've tried a lot. When I start the “Remove all existing XMP” script and then save the metadata again, it works. But the script doesn't always work. It works once out of 20 attempts.

So there are 2 problems.
1. Why are the higher-level fields not written?
2. Why doesn't the script “Remove all existing XMP” always work?

hc_431.png
hc_431.png (17.75 KiB) Viewed 579 times
hc_432.png
hc_432.png (84.56 KiB) Viewed 579 times
Regards, Bongo
Photo Supreme V6 Single User Edition, Windows 10.

fbungarz
Posts: 1630
Joined: 08 Dec 06 5:03
Location: Arizona, USA

Re: Why are the higher-level fields not written?

Post by fbungarz » 25 Feb 21 0:54

Hi Bongo,
the screenshots do not show how you have mapped your labels.

Here is how my labels are mapped:
Mapping_to-DWC.jpg
Mapping_to-DWC.jpg (232.04 KiB) Viewed 558 times
By enabling "process parent mapping" the next label further up in the hierarchy gets also processed (but not ALL of the parents, only the next one up).
If you want to make sure ALL parents are processed, they ALL need to be mapped to the correct fields and for all of them "process parent mapping" needs to be checked:
Mapping_to-DWC_02.jpg
Mapping_to-DWC_02.jpg (204.22 KiB) Viewed 558 times
This seems quite cumbersome, but the good thing is that you can actually configure the label details for several labels all in one go, here:
Mapping_to-DWC_03.jpg
Mapping_to-DWC_03.jpg (223.69 KiB) Viewed 558 times
That of course works only for labels that are at the same rank in your taxonomic hierarchy (so all the species map to dwc:scientificName, all the genera to dwc:genus, all the families to dwc:family, etc.)

Hope that helps.

Cheers,
Frank

Bongo
Posts: 46
Joined: 22 Mar 10 19:11
Location: Ingolstadt, Germany
Contact:

Re: Why are the higher-level fields not written?

Post by Bongo » 25 Feb 21 12:47

Hi Frank,

I assigned the labels as you described. I did not select "Process parent mapping" because I selected it in the Preferences. But I also tried the way you described it.
With new photos, it works as desired. That means the settings are correct. But it doesn't work with the old photos.
Regards, Bongo
Photo Supreme V6 Single User Edition, Windows 10.


Bongo
Posts: 46
Joined: 22 Mar 10 19:11
Location: Ingolstadt, Germany
Contact:

Re: Why are the higher-level fields not written?

Post by Bongo » 03 Mar 21 13:06

Hi Frank,

I removed the label from the photo, saved it, added it back and saved it again. Nothing changes.
Unfortunately, I can't use Darwin Core like this.
Regards, Bongo
Photo Supreme V6 Single User Edition, Windows 10.

Bongo
Posts: 46
Joined: 22 Mar 10 19:11
Location: Ingolstadt, Germany
Contact:

Re: Why are the higher-level fields not written?

Post by Bongo » 03 Mar 21 14:01

Somehow it seems to be a problem with Darwin Core after all. Without a hierarchy, I have specified the fields in the mapping. Only the Darwin Core fields are not written.
hc_440.png
hc_440.png (69.67 KiB) Viewed 460 times
hc_441.png
hc_441.png (10.04 KiB) Viewed 460 times
I don't know why "Familie" is written. I tried something before.

Only Taxon Family can be found in the XMP.
hc_442.png
hc_442.png (24.86 KiB) Viewed 460 times
Regards, Bongo
Photo Supreme V6 Single User Edition, Windows 10.

fbungarz
Posts: 1630
Joined: 08 Dec 06 5:03
Location: Arizona, USA

Re: Why are the higher-level fields not written?

Post by fbungarz » 04 Mar 21 19:12

Hi Bongo,
hhmmm...
I am not quite sure what is going on. It looks like I am using things quite differently. My mapping schema is typically 1:1, you are trying to write one label simultaneously into several XMP fields - correct?
In your example it seems your label is configured to write Test Item with its parent Test into "decription", "title", and several DarwinCore fields. Correct?
My mappings are one label written into one DarwinCore field, e.g., the name of a lichen "Buellia spuria (Schaer.) Anzi" into the XMP-dwc field "scientificName". Then I do have also checked the box "process parent mapping" and have the next field higher up, the parent "Buellia" mapped to "genus", that one again has its parent processing enabled, so that "Caliciaceae" is written into "family". It generally works on my system.
What does usually not work so well, is if I want to remove a label. Clearing the label does not necessarily remove the XMP entry. I have to delete those manually. An alternative is "clearing" one label metadata entry by assigning another one. But in that case the "Unassign labels with same parent" needs to be configured as "Yes".

Perhaps what you are trying to do - writing one and the same label into several fields simultaneously creates a conflict? In my case, if I want one lable to fill in several fields I configure the label with "apply detail profile".
I assigned the labels as you described. I did not select "Process parent mapping" because I selected it in the Preferences.
I am not aware that there is a option in Preferences that generally processes all parent mappings. Where is that supposed to be? I cannot find that option on my system. The "process parent mapping" is not the same as the option to "include all parent level labels as keywords". That option simply writes all higher level labels as separate keywords, it does not "assign" the parent level labels.

I hope you can figure it out. It works pretty well on my system. But when Hert first agreed to implement DarwinCore XMP support it was pretty buggy and we went back and forth until it all finally worked. It would be a pain if it still doesn't work correctly on your system. If you can reproduce the steps, which fields are written (or not) perhaps best file a bug report in Mantis?
I am really interested to know that this will actually work, because some collaborators are planning to eventually also use this...

Keep me posted.

Cheers,
Frank

Bongo
Posts: 46
Joined: 22 Mar 10 19:11
Location: Ingolstadt, Germany
Contact:

Re: Why are the higher-level fields not written?

Post by Bongo » 12 Mar 21 18:40

Through a tip from Frank, I made a label in the Detail Profile where the contents of the fields of Darwin Core is deleted.
hc_455.png
hc_455.png (90.1 KiB) Viewed 333 times
Then label added, saved, label removed, saved.

From this time everything is written as it should. Also in the hierarchy.
Strangely, the photos had a problem with whom I played and tested and all over the family of Amarillisgewächs. Now new and old photos work. And if it does not work, I do that with the label "Delete Fields".
But it would be interesting why that happened. But I can not reproduce it anymore.
Regards, Bongo
Photo Supreme V6 Single User Edition, Windows 10.

Post Reply