Project

General

Profile

« Previous | Next » 

Revision 9390

add section for CN vs MN endpoints for MetacatUI. https://projects.ecoinformatics.org/ecoinfo/issues/6532

View differences:

docs/user/metacat/source/themes.rst
187 187
For more information about ``Backbone.js``, see the Backbone.js documentation at `www.backbonejs.org <http://www.backbonejs.org>`_
188 188

  
189 189

  
190
Using Custom Endpoints
191
-----------------------
192
MetacatUI can also be configured to use custom DataONE endpoints for both Member Node and Coordinating Node APIs.
193
The ``dataone`` theme shows an example of this endpoint customization in the ``AppModel.js`` file.
194
In custom themes, the AppModel.js values can be edited to suit your particular deployment needs.
190 195

  
196
For querying the DataONE Coordinating Node, for example, the following properties would be set:
197

  
198
	::
199
	  		
200
	  	context: '',
201
		d1Service: "/cn/v2",
202
		d1CNBaseUrl:  "https://cn.dataone.org",
203
		d1CNService: "/cn/v2",
204
	
205
	
206
But querying a Metacat Member Node would be configured as:
207

  
208
	::
209
	  		
210
	  	context: '/metacat',
211
		d1Service: '/d1/mn/v2',
212
		d1CNBaseUrl: "https://cn.dataone.org/",
213
		d1CNService: "cn/v2",
214

  
215

  
216

  
191 217
Creating a Custom Skin
192 218
----------------------
193 219
.. deprecated:: 2.2.0

Also available in: Unified diff