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
For communicating changes between data package revisions.
Implementation ideas:
User calls make_eml() with return.obj = TRUE, constructs and adds the changeHistory nodeset themselves, then calls EML::write_eml(). NOTE: This requires a solution to the workaround at make_eml()line 1382.
template_change_history(), a new function returning a tab-delimited template with changeHistory nodes as fields.
The text was updated successfully, but these errors were encountered:
Much of template_change_history()'s return could be auto-generated based on a sequence of EML files. This may lower the activation energy enough for users to actually report this info.
For communicating changes between data package revisions.
Implementation ideas:
make_eml()
withreturn.obj = TRUE
, constructs and adds the changeHistory nodeset themselves, then callsEML::write_eml()
. NOTE: This requires a solution to the workaround atmake_eml()
line 1382.template_change_history()
, a new function returning a tab-delimited template with changeHistory nodes as fields.The text was updated successfully, but these errors were encountered: