Recent changes have caused mdEditor to be specific to the NGGDPP environment, rather than being a general tool. This issue is about splitting the core profiles from the extra profiles that will be part of the NGGDPP environment.

The end result of this should be 2 files: coreProfiles.json and nggdppProfiles.json

They should be formatted the same as profiles-list.json.

This is an intermediate step in the process of removing NGGDPP from the core/default mdEditor environment.

This issue will require changes to the mdEditor to support a secondary url for the NGGDPP profiles to be loaded.

The current default profiles (basic, full, project, product) do not have version numbers. They are all currently listed as "VERSION". Prior to next merge to master set all versions to 1.0.0 (or whatever is appropriate).

I have a profile and would like to prevent the extent (and keywords) tabs from showing up. I am trying to make this work with the extent first. I have

1. removed extent from the nav section and
2. set the extent section to false in the json, i.e. "extent": false,

but the tab still shows up. Also, if you select the tab, the whole extent section shows up in the editor...

I seem to be missing something very simple...

The profile is at https://raw.githubusercontent.com/tedhabermann/NDC_Profiles/main/BOEM_Template.json

Create a changelog file to record major updates to the profiles.

There may no longer be a need for the NPM mdprofiles package. The new workflow is evaluating the use of jsDelivr which will cache the information from some authoritative source (e.g. GitHub repository). The last NPM package created was mdProfiles version 0.2.5-rc1

mdProfiles has been removed as an npm module dependency from mdEditor in the version using dynamic/custom profiles. I'm pretty sure that the only change in this commit that will actually do anything is to the file /resources/profiles/full.json. Unless this module is being used outside of mdEditor, then the files related to packing this as an npm module can be removed.

I just wanted to point that out, it's not a concern and will not cause any issues.

Originally posted by @jwaspin in #29 (comment)

Reverting back to having mdProfiles only supporting the core profiles, so NGGDPP profiles need to be removed.

See mdEditor issue: adiwg/mdEditor#550

@jwaspin I think you might be the only one working in this repo. The name change would make this consistent with the most other repos, which use develop as the default.

Any thoughts??

• #60
• #61
• Testing w/ mdEditor v1.0.x

Merge develop -> master

Merge recent dev changes into master

Update profiles-schema.json to support associating one or more custom vocabularies with a profile.

See:

• adiwg/mdEditor#550
• adiwg/mdEditor#566

Update full profile to support data quality additions (http://wiki.esipfed.org/index.php/DQ_DataQuality)

See:

• adiwg/mdJson-schemas#203
• adiwg/mdJson-schemas#256

The current default profiles do not have version numbers. They are all currently listed as "VERSION". Update version numbers for:

• basic
• full
• product
• project

Use version 1.0.0

The current documentation references an older version of the schema.

There may be other details that need updating but the existing profiles are still the same ones, not sure if they changed internally.

• Add vertical extent to full-map
• Add temporal extent to full-map
• Update profiles with vertical and temporal extents
  • basic
  • product
  • project

• #59

Create a configuration file that can be used by the mdEditor to specify the default set of profiles (profiles-list.json?)

This will be required to support adiwg/mdEditor#550.

The documentation should be updated to describe the format of the configuration file and how to configure the mdEditor to use the file.