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

The "filters" field in the manifest strand should be used to validate the datasets specified in the manifest #74

Open
cortadocodes opened this issue Apr 6, 2021 · 2 comments
Assignees
Labels
decision needed A decision is required (e.g. on UX or company policy)

Comments

@cortadocodes
Copy link
Member

Feature request

Use Case

The filters field in the manifest strand should be used to validate the datasets specified in the manifest

Current state

No validation takes place.

@cortadocodes cortadocodes self-assigned this Apr 6, 2021
@thclark thclark added this to Highest Priority in Twined Ecosystem Roadmap May 10, 2021
@thclark thclark moved this from Highest Priority to In Progress in Twined Ecosystem Roadmap May 10, 2021
@thclark
Copy link
Collaborator

thclark commented May 10, 2021

This should be subsumed within the tag templating work for file metadata.

@cortadocodes
Copy link
Member Author

Do we want to fully enable the Lucene search syntax here or just use JSON validation? @thclark

@thclark thclark added architecture decision needed A decision is required (e.g. on UX or company policy) labels Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
decision needed A decision is required (e.g. on UX or company policy)
Projects
Status: Priority 1 (Low)
Development

No branches or pull requests

2 participants