Talking about Data Entry Questions

[jobdiogenes]

Column Properties, Data Entry Behavior and UI

What we expect from Collumn properties interface?

some tips (popup may be) with examples and some way to get help about. (icon/ ?) where could open an URL to that. Like Google Did with Spreadsheets. Patterm for example could have a popup with "Regex Javascript Standard, doc at (urllink)"

What we expect when type to a cell in a column ?

the same behavior as other Form with defined data type and validation. Which means by example when you set a column type to a number, user can only type numbers and separators if are not integers. if you defined a Date, screen format (ex: yyyy-mm-dd) must be followed. An enumerator, could be auto-complete. In simple word, restriction and formats must be strict while typing.

What we want when type new Data?

While type to sheet grid is common. Its slow and counterintuitive. Input data as Form, are much better and we could set to use instead to go to next field. As data-curator,m already has column (field) definition. Its possible and not so hard to imputing data as a Form, which are build in the fly.

What we expect when importing data to an already defined constraints ?

Has an option that did validation while importing, and in the UI shows which cells and lines has problems. And we can also make filters that only show lines with problems.

[ghost]

Hi @jobdiogenes Thanks for the feedback - there seem to be quite a few ideas in this one issue. Unfortunately with the amount of time our sponsors have given us for this year, it's unlikely that I can get to these anytime soon.

What we expect from Column properties interface?: I like the idea of more help text e.g., pointer to regex doco for pattern. There's probably a few others that could be amped up. Some more specifics or even PR might help with being able to get changes in (as little effort then required by me).

What we expect when type to a cell in a column ? I think what you're saying here is that a 'clicked' Validation or Check when 'Export' is 1 (or 2) thing(s), but it would be nice to actually have the app enforce any rules on the fly. I guess we could consider which validation rules this would work for (e.g., yes dates is a good one, but on the other hand, requiring 'no blanks' would be a little more tricky as a cell will be empty on init). Again, unfortunately at this stage with current allocation, without a PR, it's unlikely we'll have the time to achieve something like this.

What we want when type new Data? Not quite sure what you mean here - perhaps some more explanation?

What we expect when importing data to an already defined constraints ? So here if I've understood correctly, yes agreed filtering is a nice idea - it did come up in initial project discussions (I may even have a previous issue which addresses this?) - again may not have time, for now, to look at this yet.

[ghost]

Hi @jobdiogenes

• Tooltips: If there are specific tooltips you'd like to see implemented with either a PR or you could use the existing templates as examples for just providing tooltip text for me (see under: https://github.com/ODIQueensland/data-curator/tree/develop/src/renderer/mixins, where there are files names ending in : .....Tooltip.vue, and you can get the gist of the text under any of the keys labelled: 'template'. for example: Table property->foreign key(s) : 'A must exist in the referenced table and column(s)' is enough for me to consider adding these (as each is usually straightforward)

• Validation on-the-fly: I like strict validation while typing (instead of waiting to click 'Validate') but there won't be enough time for this release, apologies. It's an issue I'll keep open as it would be nice to add this for more development time.

• Forms: Not sure if this is about importing metadata only or opening an existing say, Excel spreadsheet? We can import an Excel spreadsheet:

and we are looking at considering #987 , or is this something else?

• Filters: Again yes I'll keep this open, but unfortunately won't have the time to put this in now, but something I'd like to raise in future with more allocation.

GitHub

ODIQueensland/data-curator

Data Curator - share usable open data. Contribute to ODIQueensland/data-curator development by creating an account on GitHub.