Skip to content

Create restrictions on file fields #231

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

Closed
nagem opened this issue Mar 31, 2016 · 4 comments
Closed

Create restrictions on file fields #231

nagem opened this issue Mar 31, 2016 · 4 comments
Assignees

Comments

@nagem
Copy link
Contributor

nagem commented Mar 31, 2016

Use an enum in our input json schema to restrict values saved to type and modality fields

@nagem nagem self-assigned this Mar 31, 2016
@nagem
Copy link
Contributor Author

nagem commented Mar 31, 2016

Also incorporate #210

@nagem nagem changed the title Create restrictions on filetype, modality and instrument fields Create restrictions on file type, modality and measurement fields Mar 31, 2016
@nagem nagem changed the title Create restrictions on file type, modality and measurement fields Create restrictions on file fields Mar 31, 2016
@nagem
Copy link
Contributor Author

nagem commented Mar 31, 2016

@gsfr I had written down file type, modality and "instrument" when I think perhaps I meant measurement? Please confirm the fields we want to restrict to a list of approved values when you get a chance.

@gsfr
Copy link
Member

gsfr commented Apr 4, 2016

Yup. File type and modality are easy. Measurement is harder, because it depends on modality.

@nagem
Copy link
Contributor Author

nagem commented Oct 17, 2017

Encompassed/replaced by #649

@nagem nagem closed this as completed Oct 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants