You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...so that I can provide some baseline documentation for an LDD, beyond the schema/schematron.
π Additional Details
Similar to the existing index.html output that comes from lddtool -p
Acceptance Criteria
Given an IngestLDD for a discipline LDD When I perform `lddtool --pds4 --ldd --html PDS4_LCROSS_IngestLDD_1100.xml Then I expect the schema and schematron to be output as per usual, as well as an HTML document, similar to the existing PDS4 IM Spec, but specifically for this LDD.
βοΈ Engineering Details
Note: This has already been partially implemented with the --im_specification flag. Some updates needed:
change flag to -h and --html respectively
the output HTML includes both the core and the LDD in question. that is fine, but we should move the LDD content towards the top, and update the boilerplate text to be more LDD-focused.
π Integration & Test
No response
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Data Engineer
πͺ Motivation
...so that I can provide some baseline documentation for an LDD, beyond the schema/schematron.
π Additional Details
Similar to the existing
index.html
output that comes fromlddtool -p
Acceptance Criteria
Given an IngestLDD for a discipline LDD
When I perform `lddtool --pds4 --ldd --html PDS4_LCROSS_IngestLDD_1100.xml
Then I expect the schema and schematron to be output as per usual, as well as an HTML document, similar to the existing PDS4 IM Spec, but specifically for this LDD.
βοΈ Engineering Details
Note: This has already been partially implemented with the
--im_specification
flag. Some updates needed:-h
and--html
respectivelyπ Integration & Test
No response
The text was updated successfully, but these errors were encountered: