Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update LDDTool to write the PDS4 Data Dictionary (DocBook) for multiple LDDs #93

Closed
jshughes opened this issue Dec 2, 2019 · 7 comments
Labels
enhancement New feature or request i&t.skip

Comments

@jshughes
Copy link
Collaborator

jshughes commented Dec 2, 2019

Update LDDTool to write the PDS4 Data Dictionary (DocBook) for multiple LDDS. Multiple LDDs can now be stacked to produce a combined PDS4 Data Dictionary.

@jordanpadams jordanpadams changed the title Multi_LDD_DataDictionary Update LDDTool to write the PDS4 Data Dictionary (DocBook) for multiple LDDs Dec 2, 2019
@jordanpadams jordanpadams added the enhancement New feature or request label Dec 2, 2019
jshughes416 pushed a commit that referenced this issue Dec 2, 2019
Update LDDTool to write the PDS4 Data Dictionary (DocBook) for multiple LDDS. Multiple LDDs can now be stacked to produce a combined PDS4 Data Dictionary.
jshughes added a commit that referenced this issue Dec 2, 2019
@jshughes jshughes closed this as completed Dec 3, 2019
@rchenatjpl
Copy link

  1. Is the output docbook the xml version of the Information Model Specification, https://pds.jpl.nasa.gov/datastandards/documents/im/current/index_1D00.html?
  2. Should the output docbook include anything from the input Ingest_LDD for lddtool? I didn't see any.
  3. Do you know an easy way to view or convert the docbook file?
    Thanks

@rchenatjpl
Copy link

Regarding the previous comment's #2, I meant, does the docbook have anything from the LDD that's getting created? I didn't see any, but then I changed Ingest_LDD/namespace_id from "insight" to "geo", and that worked. Is this intentional? That would be fine. Is it documented somewhere? Eh, this stuff doesn't matter much except that I must test it. I won't chase this down any further.

@jordanpadams
Copy link
Member

@jshughes can you comment? I thought this should work for both mission and discipline dictionaries but maybe not?

@rchenatjpl
Copy link

ah, an older version of lddtool showed what namespaces were available, and "insight" wasn't one of them. I guess it'd be nice to see what that list is, though since presumably Steve's the only one generating the DocBook, not having that info is a pain only for the tester.

@jshughes
Copy link
Collaborator Author

jshughes commented Apr 9, 2020

Yes, there is an issue assigned to me to reduce the number of messages written by LDDTool to the log. The list of namespaces was considered debugging information and is now only written when the debug flag is set to true. Unfortunately, the debug flag is set in the code.

However, the namespace registry can be found here: https://pds.jpl.nasa.gov/datastandards/schema/pds-namespace-registry.pdf

@jordanpadams
Copy link
Member

@jshughes can we maybe output this in the Help (-h) info?

@jshughes
Copy link
Collaborator Author

Good idea, will add add this suggestion to the queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request i&t.skip
Projects
None yet
Development

No branches or pull requests

3 participants