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

mdJson metadata object required #188

Open
stansmith907 opened this issue Feb 19, 2018 · 4 comments
Open

mdJson metadata object required #188

stansmith907 opened this issue Feb 19, 2018 · 4 comments
Labels

Comments

@stansmith907
Copy link
Contributor

Maybe. Currently at the top schema level only the schema and contact objects are required. It seems the metadata object should also be required - at least if the record is being sent through the translator. I can see saving an mdJson object with just contacts for the mdEditor, but that should never be passed to the mdTranslator. From an mdTranslator perspective there should always be a metadata object, thus the schema should back that up.

@jlblcc
Copy link
Member

jlblcc commented Apr 6, 2018

I can implement this now, but we did discuss the possibility of just having a dataDictionary, i.e. for ISO 19110 output. Do we want to revisit that or just require metadata only?

@stansmith907
Copy link
Contributor Author

Yep, you're right forgot about dictionary only option. Close this one.

@jlblcc
Copy link
Member

jlblcc commented Apr 12, 2018

We can require at least one of dataDictionary or metadata?

@jlblcc jlblcc modified the milestones: 2.4.6, 2.4.7 Apr 12, 2018
@stansmith907
Copy link
Contributor Author

Unless we also want to just hold a bundle of contacts. Although that may not be of any value to the translator, the editor may also want to use the schema. We can just leave it as is for the schema and this can be a translator check only.

@jlblcc jlblcc added question and removed bug labels Sep 25, 2018
@jlblcc jlblcc removed this from the 2.4.9 milestone Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants