WIPACrepo / file_catalog

Store file metadata information in a file catalog
MIT License
1 stars 4 forks source link

Metadata Typing #80

Closed ric-evans closed 3 years ago

ric-evans commented 3 years ago
ric-evans commented 3 years ago

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

ric-evans commented 3 years ago

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

dsschult commented 3 years ago

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

Fair enough.

ric-evans commented 3 years ago

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

Fair enough.

https://github.com/WIPACrepo/file_catalog/issues/81