search

tetherless-world / opendap

Provenance trace and pingback services for OPeNDAP using Prizms.
http://opendap.tw.rpi.edu
1 stars 1 forks source link

prov_module configuration to write into share/hyrax as alternate to Prizms' SDV. #42

Open timrdf opened 10 years ago

timrdf commented 10 years ago

Extension to #24; include configuration parameter(s) to write into directory share/hyrax instead of Prizms' SDV directory. This is to allow Prizms to provide the provenance publishing from a different server, so that Prizms need not be installed on the same server that OPenDAP is on. The admins would only need to add prov_module to get provenance publishing.

Add param to prov_module/prov.conf.in

timrdf commented 10 years ago

While trying name the variable, BES.Catalog.catalog.RootDirectory=/opt/opendap/branch/share/hyrax in etc/bes/bes.conf specifies the "htdocs" directory.

So, instead of Prov.cr_data_root=/home/prizms/prizms/opendap/data/source when using a local Prizms, we could say Prov.self_root=prov to mean "write into directory prov from BES.Catalog.catalog.RootDirectory, i.e. /opt/opendap/branch/share/hyrax/prov". Or, we could just require that the Prov.self_root specify an absolute path to provide more flexibility.

If Prov.cr_data_root and Prov.self_root are set to valid paths, write to both? Make soft links from self_root to cr_data_root (since Prizms version controls and we'd want the actual values)?

We're trading off consistency with flexibility.

31 Jan we decided that we are going relative "prov" not absolute.

timrdf commented 10 years ago

What's the easiest way for a client to access all new files in a given OPeNDAP directory (e.g. http://opendap.tw.rpi.edu/tomcat/opendap/hyrax/prov)? Prizms will need to figure that out to set up shop on the remote server.

timrdf commented 10 years ago

Supports #41