sbJson 2.0 browseCategories

[stansmith907]

Mapping of sbJson browseCategories to mdTranslator internal data structure:

• reader complete
• writer complete

{
   "browseCategories": [
      "Data",
      "Publication",
      "Project",
      "Physical Item"
   ]
}

Definition: A type of tag that defines the category of an item. These are mostly set internally by ScienceBase.

Mapping...

• browseCategories: The tag value.
  Map to: [schema][metadata][resourceInfo][resourceTypes][n].type
  view mdTools

---

Mapping to mdTranslator

   def newBase
      intObj = {
         metadata: {
            resourceInfo: {
               resourceTypes: [
                  {
                     type: 'Data',
                     name: ''
                  },
                  {
                     type: 'Publication'
                  },
                  {
                     type: 'Project'
                  },
                  {
                     type: 'Physical Item'
                  },
               ]
            }
         }
      }
   end

Translation to mdJson

{
   "metadata": {
      "resourceInfo": {
         "resourceType": [
            {
               "type": "Data"
            },
            {
               "type": "Publication"
            },
            {
               "type": "Project"
            },
            {
               "type": "Physical Item"
            }
         ]
      }
   }
}

[stansmith907]

In mdTranslator and mdJson resourceType < type is an ISO code selected from MD_ScopeCode. The browseCategories in the above example are included in MD_ScopeCode as well except for"Physical Item", but there may be appropriate substitutes in MD_ScopeCode. I'm not sure how browseCategories are used so can't really suggest using the ISO codes instead.

[stansmith907]

The ScienceBase is an enumerated list, cannot be extended.
Not all ScienceBase items have a browseCategory.

Writing:

• always write 'data' tag
• if project write 'project'
• others if they map to non-ambiguous tags
• may 'physicalItem' to our code list
• write all mdJson 'resourceTypes' to tags (see sbJson 2.0 tags #69)

Reading:

• map the ones that are non-ambiguous tags
• if blank set as 'dataset'