Project

General

Profile

« Previous | Next » 

Revision 6885

Added by Matt Jones over 12 years ago

Continued authoring the description of DataONE in Metacat. More to come.

View differences:

configuration.rst
336 336

  
337 337
   Configuring Geoserver.
338 338

  
339
DataONE Configuration
340
~~~~~~~~~~~~~~~~~~~~~
341
Metacat can be configured to operate as a Member Node within the DataONE
342
federation of data repositories.  See :doc:`dataone` for background and details
343
on DataONE and details about configuring Metacat to act as a DataONE Member Node.
344

  
345
Replication Configuration
346
~~~~~~~~~~~~~~~~~~~~~~~~~
347
Metacat can be configured to replicate its metadata and/or data content to another
348
Metacat instance for backup and redundancy purposes, as well as to share data across
349
sites.  This feature has been used to create the Knowledge Network for Biocomplexity
350
(KNB), as well as other networks.  See :doc:`replication` for details on
351
the replication system and how to configure Metacat to replicate with another node.
352

  
353
.. Note:: 
354
  
355
  Note that much of the functionality provided by the replication subsystem in Metacat
356
  has now been generalized and standardized by DataONE, so consider utilizing the
357
  DataONE services for replication as it is a more general and standardized approach
358
  than this Metacat-specific replication system.  The Metacat replication system
359
  will be supported for a while longer, but will likely be deprecated in a future
360
  release in favor of using the DataONE replication approach. 
361

  
339 362
Additional Configuration
340 363
------------------------
341 364
The most dynamic Metacat properties are managed and modified with the 

Also available in: Unified diff