Check min and max length on all inputs and complain where appropriate.

[rossjones]

No description provided.

[gtdata]

As the content is trying to educate users about why they should stick to under 65 characters - is there a way we enforce this? Like Twitter do... @rossjones @maxf @BlancaTortajada

[maxf]

@gtdata: yes, it's possible. More specific questions:

1. should we let the user save a draft with a title longer than 65 characters
2. should we let the user publish a dataset with a title longer than 65 characters (or do we just warn them)?
3. Same questions apply to description + what is the limit in characters?

[rossjones]

The benefit of imposing restrictions here, is that when users edit existing datasets from the old site, we can enforce the new rules. So those datasets with very long titles we can force to be shortened.

[davidread]

I think it should only be enforced on dataset creation. Occasionally we've had this situation in the past, where someone edits a dataset to change something and it blocks you until you fix something else unrelated. It's just caused confusion and support requests - "why is it complaining, what is wrong with my change?" not understanding it is a different in the error message, even with a pretty clear message and red box drawn around the field with the problem.

[maxf]

@davidread if it was enforced all the time, not just on creation, then people editing the dataset would only get error messages on what they just changed, no?

[davidread]

Yes for ones created on the new system - that would work. It's the legacy datasets I'm concerned about.

[maxf]

Ah, I see. Makes sense for those.

…

On 17 February 2017 at 14:35, David Read ***@***.***> wrote: Yes for ones created on the new system - that would work. It's the legacy datasets I'm concerned about. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#281 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEPpp85Vhg15G3BGi964S0c23sVyG2Vks5rdbBNgaJpZM4L5y6-> .