Feature #4039
Updated by Skye Roseboom over 10 years ago
D1 index processing has been integrated into metacat MN stack as as search provider.
This class assumes CN operations:
-using /etc/dataone/node.properties to configure the hostname part of the resolve URL
-using 'cn' in the resolve url as part of the rest api (hostname/cn/v1/resolve/pid)
Possible to refactor the class to optionally look for hostname and cn/mn from metacat configuration if dataone configuration file is not available. This would allow the ResolveSolrField to operate in both a CN and MN metacat environment.
Matt mentioned metacat.properties as a source for this information:
{metacat web app context}/WEB-INF/metacat.properties
it contains properties:
server.name
dataone.nodeType
May also need base url info to append to host name before the /mn/v1/resolve/ path part?
In the search index - the 'dataUrl' and 'fileID' fields are filled by this class.
This class assumes CN operations:
-using /etc/dataone/node.properties to configure the hostname part of the resolve URL
-using 'cn' in the resolve url as part of the rest api (hostname/cn/v1/resolve/pid)
Possible to refactor the class to optionally look for hostname and cn/mn from metacat configuration if dataone configuration file is not available. This would allow the ResolveSolrField to operate in both a CN and MN metacat environment.
Matt mentioned metacat.properties as a source for this information:
{metacat web app context}/WEB-INF/metacat.properties
it contains properties:
server.name
dataone.nodeType
May also need base url info to append to host name before the /mn/v1/resolve/ path part?
In the search index - the 'dataUrl' and 'fileID' fields are filled by this class.
