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

reconsider list requirements #16

Open
arlin opened this issue Apr 5, 2016 · 0 comments
Open

reconsider list requirements #16

arlin opened this issue Apr 5, 2016 · 0 comments

Comments

@arlin
Copy link
Member

arlin commented Apr 5, 2016

We ran into a problem with a list not being processed because had NA or blank for the "published" date. This is undesired behavior, because users may wish to submit lists that are not published at all.

The issue is to re-think what we are requiring. Which fields are essential for which use-cases? Which fields are essential for all use-cases?

Write a brief description and analysis of this problem and present it to the group for discussion. Then we will make decisions about how to implement lists, and document the requirements in our docs.

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

1 participant