-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow IPT to map non darwin core fields easily to the dynamicProperties field #1403
Comments
Hi Ainsof, I know this was a while ago — what fields did you have in mind for inclusion in dynamicProperties? It's generally better if fields are mapped to terms (including new Darwin Core terms if required), or extensions (including new extensions if required). |
Hi Matt, In the current process you map what you can to darwin core properties and this is done easily with the existing UI. When you want to include some non-darwin core values you need to use a tool offline like excel and concat formulas to format them as json style dynamicProperties then reupload your data. What I am proposing is an enhancement to the current UI. Perhaps all fields that cannot be mapped to darwin core can be easily mapped to the dynamicProperties field. The UI could present a "key/value" pair, where the user would enter the "key", against an existing unmappable property. When published the IPT could format these key/value pairs into a compatible json format as a dynamicField. |
I think you're describing what Sylvain has been implementing in #1613, although he's proposing all unmapped fields are added to dynamicProperties. |
Ah yes. That may be a more common use case. Perhaps a way to unselect
unwanted fields as an enhancement to that if there is a need
…On Tue, 17 Aug 2021, 02:14 Matt Blissett, ***@***.***> wrote:
I think you're describing what Sylvain has been implementing in #1613
<#1613>, although he's proposing all
unmapped fields are added to dynamicProperties.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1403 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACY7IP4G5H7YZGNQD4C25S3T5EFMTANCNFSM4E2X656Q>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Darwin Core currently provides a catch all field which allows non Darwin Core fields to be captured in the dynamicProperties field http://rs.tdwg.org/dwc/terms/index.htm#dynamicProperties
It would be great if the IPT could allow the user to easily map the "Unmapped columns" to the dynamicProperties field in JSON format. Also allowing the user to provide an alternative title for the columns that are mapped.
Currently, this has to be done outside of the IPT using something like Excel and a complex concatenate formula.
The text was updated successfully, but these errors were encountered: