Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hola Chiara, To "enrich" the TDS catalog you can use XML namespaces [1]. That allows to use more than one XML schema. In fact the TDS already uses it for the datasetScan to point using XLink schema to the directories been scanned. With respect to the datasetScan feature to create a proxy of an absolute latest atomic dataset, it would require to create an new datasetScan element. Meanwhile you can create/modify the catalogs using an external tool. I would recommend use a tool/library which is XML "aware" to guarantee well formed and semantically correct XML documents, but using other tool would fit your purpose. Take into account that catalog entries generated by datasetScan are created in-memory and they are cached/persisted (???) In specific storage format. One interesting feature in the TDS5.0 version are the dynamic catalogs, similar to a catalogScan. But it has not been officially released but the current beta version already implements it. Antonio S. Cofino [1] https://www.w3schools.com/xml/xml_namespaces.asp On 19 Jul 2018 12:37, "Chiara Scaini" <saetachiara@xxxxxxxxx> wrote: Hi all, I'm setting up a thredds catalog to be used by Geonetwork. The catalog contains meteorological data, but will be enriched by other data sources (ex. a table containing the list of records that were moved to a backup facility and are no longer available on disk, or a table containing pictures related to the files). Is it possible to enrich the xml file with other data (ex. inserting xml nodes directly into the file) without breaking thredds functionalities? What strategy do you recommend (ex. a bash script to modify the xml, or...?). Note that I'm using a <datasetScan> to recursively get all items in a nested folder structure, so I would like to modify the 'real' xml catalog that contains all the nodes (some information should to be inserted at the container level, others at the data level). Many thanks, Chiara -- Chiara Scaini _______________________________________________ NOTE: All exchanges posted to Unidata maintained email lists are recorded in the Unidata inquiry tracking system and made publicly available through the web. Users who post to any of the lists we maintain are reminded to remove any personal information that they do not want to be made public. thredds mailing list thredds@xxxxxxxxxxxxxxxx For list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
thredds
archives: