You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each member repository has its own node capabilities document that gets updated on the Coordinating Node using the CN.updateNodeCapabilities() call. An example node document is https://cn.dataone.org/cn/v2/node/urn:node:ARCTIC (be sure to view the XML source). On the CN, the node documents have a number of CN-managed properties, like:
<propertykey="CN_operational_status">operational</property>
<propertykey="CN_date_operational">2016-12-01T00:00:0.000Z</property>
<propertykey="CN_node_name">Arctic Data Center</property>
<propertykey="CN_logo_url">https://raw.githubusercontent.com/DataONEorg/member-node-info/master/production/graphics/web/ARCTIC.png</property>
<propertykey="CN_date_upcoming">2016-04-05T00:00:0.000Z</property>
<propertykey="CN_info_url">https://arcticdata.io/</property>
<propertykey="CN_location_lonlat">-119.69,34.42</property>
Change the DataONE homepage to pull the logos and other node information directly from this service using the either the CN.listNodes() call or the CN.getNodeCapabilities(nodeid) call.
By doing this, member repositories can update their information and it will propagate to the DataONE site.
The text was updated successfully, but these errors were encountered:
Just a side note: The ability to use XML data in Hugo templates is on Hugo's development road map (see gohugoio/hugo#4470). Once that feature is implemented, we could perhaps integrate member repository details like this.
And we can also think about using the browser's internal Fetch API, which reduces our dependency on JQuery. that said, we'd have to figure out a polyfill for older browsers, so, something to consider.
All this info is fetched and parsed by MetacatUI, so I've been thinking we should just create a view in MetacatUI for this and link to that page from dataone.org. Thoughts?
Each member repository has its own
node capabilities document
that gets updated on the Coordinating Node using theCN.updateNodeCapabilities()
call. An example node document is https://cn.dataone.org/cn/v2/node/urn:node:ARCTIC (be sure to view the XML source). On the CN, the node documents have a number of CN-managed properties, like:Change the DataONE homepage to pull the logos and other node information directly from this service using the either the
CN.listNodes()
call or theCN.getNodeCapabilities(nodeid)
call.By doing this, member repositories can update their information and it will propagate to the DataONE site.
The text was updated successfully, but these errors were encountered: