nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Editing the geoportal server catalog

Anonymous User

I am trying to add another tab in the Metadata Editor. Basically, I am trying to add a tab somewhere here

with two additional fields that will be saved. Can this be done?

Vind meer berichten getagd met

metadata

ArcGIS for INSPIRE

Accepted answers

Marten

Like so?

I did this by updating the myprofile files. the attached zip has the files for it.

myprofile.zip

All comments

ArunPremachandran

Hi Marten,

I'm also going through the same situation. while saving the myprofile metadata I'm getting the following error. any help will be appreciated. ( I have added the console error as well )

saveroor.PNG

console.PNG

Anonymous User

That did the trick, moving the custom profile to the top of the list. Thank you kind sir!

Marten

The interrogation rule itself looks ok. However, if you also have the base ISO 19115 profile active AND if the interrogation rule for ISO 19115 is before your custom profile, the metadata may still be interpreted as ISO 19115. That is because the rule for ISO 19115 is:

    {
      key: "iso-19115",
      requiredPath: "esri/dijit/metadata/types/iso/base/DataDocumentType",
      interrogationRules: [{
         path: "/gmd:MD_Metadata/gmd:identificationInfo/gmd:MD_DataIdentification",
         must: true
      }]
    },

And means your ISO-based metadata will still be recognized by this rule. You have two options:

Move your custom profile to the top of the list of typeDefinitions. This way the rule for your custom profile will be evaluate before the base ISO 19115 rule. Geoportal evaluates the rules in order of the list.
Remove the base ISO 19115 profile ('iso-19115') from the list of allowedTypeKeys. This will remove it entirely from the editor.

Anonymous User

In ...\geoportal\app\context\metadata-editor.js, I added the custom profile like so

When you say "you will want to set the metadata standard/version to your profile", do you mean I have to set the interrogationRules path to the local path of the custom profile? I don't quite understand that part 🙂

Marten

One additional note. The Geoportal Server will look at the metadata and based on some rules decide what is the best fitting profile. If you create a profile for example of ISO 19115, you will want to set the metadata standard/version to your profile. OR if you have additional elements you can test for those.

In ...\geoportal\app\context\metadata-editor.js you will find the typeDefinitions. You added your custom profile here already. Look for the interrogationRules field in your custom profile and change its content to one or more paths, values, and must fields so that your profile is distinguished from other profiles.

Anonymous User

@Marten here's a LINK to the my catalog, hopefully someone can figure out what I am missing because I sure haven't figured it out yet.

Anonymous User

screen share works for me, would be a lot more educational rather than me uploading my files here 🙂

Marten

Shall we organize a screen share session? Will be quicker than going back and forth guessing what steps you take. OR, if you can zip your profile directory and attach here?

Anonymous User

When I go to Network, there is only one item and when I go to preview, it says this:

I was comparing the path in the interrogationRules to the ones above, but all is same, nothing stands out.

Marten

Typically this means the framework cannot find one of those JS/HTML objects that define a piece of the editor. What helps me with troubleshooting this is to follow the network traffic in the browser developer tools. This error will typically be accompanied by an HTTP 404 error to some .js file in the editor definition tree. The request before that failed one is in most cases the file that makes a bad reference or is missing the reference.

When referencing an object in GXE you need to decide whether to reference the definition as included in the JS API or to reference your own in the GXE 'tree'. Referencing objects in the JS API means you don't need to go to all the details in that object. Think for example contact info (ISO - CI_Contact). If you're happy with how the JS API defines it, you can reference CI_Contact and automatically include the elements it is composed of by including something like this in your definition:

HTML template:

<div data-dojo-type="esri/dijit/metadata/form/iso/ObjectReference"
     data-dojo-props="target:'gmd:onlineResource',minOccurs:0, 
                      label:'${i18nIso.CI_Contact.onlineResource}'">
  <div data-dojo-type="esri/dijit/metadata/types/iso/gmd/citation/CI_OnlineResource">
  </div>
</div>

The key is the data-dojo-type attribute. That is the object reference in the JS API, recognizable with esri/dijit/metadata/types/iso as the path to the ISO definition in that JS API.

If you want to change one of the elements in CI_Contact, you would create a local copy of the element with the changes and then replace the reference to JS API with one to your local app: app/gxe/types/iso.

It is important to also look at the JS file corresponding to the object that references CI_Contact and update the reference there to the local one. CI_Contact is referenced for example in CI_ResponsibleParty. That reference could be to the default one in the JS API by including the full esri/dijit... path OR it could be a reference to you local customized version by including the app/gxe path or a relative path. Since CI_ResponsibleParty and CI_Contact are in the same folder, that relative reference would be ./CI_Contact.

Anonymous User

Marten,

I have two more questions. Sometimes but not always, when choosing the custom 'MyProfile', I get this error

Also, when I try to save the profile, I get this error

Am I missing some configuration like in the case of the metadata-editor?

Anonymous User

Marten, thank you for your time and effort. I'll accept the original response as the solution 🙂

Marten

myprofile is based on ISO 19115, but the same mechanism applies if you want to extend the ArcGIS metadata profile.

Anonymous User

Yes, that did the trick. I did not know of the metadata-editor.js - Thank you kind sir!
One last question, this custom profile you have provided me with, is based of which profile? I'd like to extend the 'Arcgis metadata' but I will need to examine the custom profile you have made so that I can do it on my own. I need to extend this type

Marten

ah, that means you have not yet configured the geoportal to consider myprofile yet. to do so, you will need to edit geoportal\app\context\metadata-editor.js. That file lists the known and used profiles. You will see a list 'allowedTypeKeys' with quite some values. Those values are the keys of the active metadata profiles in your geoportal. You can remove some you don't need and then add "myprofile-iso-19115" to the list.

Then notice the list called 'typeDefinitions'. The entries in this list describe the different metadata profiles by telling geoportal where to find a profile (in the webapp structure) and how to recognize XML to be of the defined profile by an XPath expression ("path"), a criterion ("must":true) and sometimes a value. In that list insert the following JSON object:

{
  key: "myprofile-iso-19115",
  requiredPath: "app/gxe/types/myprofile/base/DataDocumentType",
  interrogationRules: [{
    path: "/gmd:MD_Metadata/gmd:metadataStandardName/gco:CharacterString",
    value: "MyProfile",
    must: true
  }]
}

Anonymous User

So, I login and go to the Admin menu, I choose Create Metadata and choose the New Document option.

From there, I have the following options

Is the myprofile profile supposed to be here or should I choose one of the above templates /profiles?

Anonymous User

I must be missing something, I did replace the existing myprofile folder but it's the same. I can't get the Ecommerce to show.

Marten

yep! just replace the existing myprofile folder with the contents of the zip. no need even to restart Tomcat. Just a 'clear browser cache' in Chrome will show the updated editor.

Anonymous User

Yes, exactly like so. Wow, thank you. I now can examine the files and use it for myself.

So how does one apply these new files /tabs /fields to the existing geoportal? I overwrite the existing 'myprofile' or is there another process?

Marten

Like so?

I did this by updating the myprofile files. the attached zip has the files for it.

myprofile.zip

Anonymous User

Hi Marten,

Thank you for the detailed reply, I really appreciate it.

I am looking to include two new items. One would be an input field for Price and the other one would be a Tax dropdown menu with 2 or 3 items in the dropdown - number with percentages (ex. 5%; 18%; 0%).
I am looking to extend any metadata, which ever one is simplest to modify /edit.
I did find the 'myprofile2' but I cannot find the esri/dijit/metadata/form/Tabs. I presume if I want to add a new tab or new field in an existing Tab, I need to do so in the /Tabs?

Marten

hi, this is indeed possible, but requires a few things:

If you are adding new elements/attributes, the underlying metadata specification needs to include your additional information also. can you share more on what items you would want to include on the new tab?
Geoportal Server includes a number of metadata formats. Although you can build an editor from scratch, typically you would start from one of the existing ones. Which metadata standard are you looking to extend?
You will find the configuration files/code for the editor in : ../geoportal/app/gxe/types. In fact there is a sample type 'myprofile' included when installing Geoportal Server.
The metadata editor (gxe = Geoportal XML Editor, it can be made to edit pretty much any XML document) uses Dojo and you will find JavaScript files declaring classes and components and a related template file that lays out the components in the preferred order.
It is best to start by looking at the 'myprofile' editor to see some of the foundations of gxe. You'll see esri/dijit/metadata/form/Tabs that results in tabs for each of the elements included and then individual dijit references for the sections in the tabs. While you could build an entire editor in a single file, you would be repeating a lot of elements. What the gxe does is break out those reusable elements all the way from a multi-select option list to an entire metadata identification section.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.