text: In a previous post I have describe how to produce documents from a baseline of a DNG module. In this post I will show how to list the baselines available for a DNG module and their metadata using RPE 1.2.1.1 and DNG 4.0.6. You can also use this technique to include in a module document the metadata information of the baseline it was generated from.
  The artifacts used in this post are available on the RPE Community Template Library.
  NOTE: this is a workaround, please follow the DNG documentation for better/official solutions.
  NOTE: this method uses DNG APIs that are not formally supported for use with RPE so it might not work with future DNG versions.
  With the disclaimers in place the process starts from the RRC Reportable REST API documentation which lists an API for getting the list of baselines for a given module. Note again the “This information cannot be reported using RPE” comment.
  On my DNG 4.0.6 server if I make the following request,*&private=true I get back the list of baselines for my modules In what looks like a Feed XML.
  The XML source confirms the assumption which means it is possible to manually create a schema for the data. The schema is available alongside the example template on DevWorks, see link above.
  NOTE: the entry point of the schema ( what you need to select when adding the schema to your template) is baselinefeed.xsd
  The schema I have created for this data exposes the what I believe are the most interesting properties as attributes of the “moduleInfo” element under feed/entry/content. The full list of properties of the baseline is available under the child binding query.
  NOTE: the elements directly under feed/entry such as author describe the feed entries and not the module baseline info.
  NOTE: the baseline attribute matches the “jfsBaseline” binding and not the “url” one as its the last segment of the jfsBaseline URL you need when filtering the module content.
  Accessing the baseline or the url does not work but you can use the baseline URL to get the baseline ID. Notice in the screenshot below that the baseline URL contains the ID I have used in the Producing documents from a baseline: _br43oB1wEeS3uL5XzNkgbg
  Using the sample template with the URL provided above produces the following document.
  4 thoughts on “Publishing DNG Module Baseline Metadata”
  Hi Dragos,
  I have attempted to use this workaround and it seems that the baselinefeed.xsd file cannot import the moduoleinfo.xsd file on my computer, because the namespace seems to be unavailable to me. As a result my schema in RPE reaches feed>entry>content>result and the tree stops there.
  I understand that if this is a change then the workaround may not work any longer (your disclaimers noted) however I wanted to check if this was a mistake on my part.
  Best Regards,
  Sam
  Sam, I just tried this with RPE 1.3 and I got the schema successfully inserted in the template and I could navigate to feed->entry->content->moduleBaseline->binding.
  See here the template I just created:
  Dragos, my mistake. I think ‘something funny’ happened and I just had to close and reopen RPE. Its working fine now.
  Thanks!
  Sam, are you using RPE 1.3?