Form templates

[NathanW2]

It would be handy to have "feature templates". These would be shown in a dropdown list at the top a new feature form when creating a feature and would have pre set values that get applied to the form when selected.

Each entry would just be a set of key value pairs of field : value that we run though and set.

The user should be able to save the template while using the form. The workflow would be:

• Enter the values you want to save
• Save As Template..
• Name it
• Done

This would allow you to have things like:

• 2m - 1080 Manhole

which might have the following values:

size: 1080
depth: 2m
type: manhole

This would speed up data entry a lot when out in the field.

[NathanW2]

There also needs to be a way to tell the form that certain fields should never be saved, something like is should work:

- config: {}
  field: pipe_no
  name: Pipe ID
  widget: Text
  template:
    ignore: True

[bzeeb]

Personally think it would be a lot of work coding from our perspective and setting up templates from an admin perspective relative to the limited use-cases. If this feature is needed then a custom form could be built.

'Feature repeat' fills part of this role already as well, not to mention the fact if templates were overused it would be very easy to make mistakes in field.

[NathanW2]

Was just an idea remember ;) On Sep 30, 2014 6:25 PM, "Ben Zeeb" [email protected] wrote:

Personally think it would be a lot of work coding from our perspective and setting up templates from an admin perspective relative to the limited use-cases. If this feature is needed then a custom form could be built.

'Feature repeat' fills part of this role already as well, not to mention the fact if templates were overused it would be very easy to make mistakes in field.

— Reply to this email directly or view it on GitHub https://github.com/DMS-Aus/Roam/issues/137#issuecomment-57281814.

[bzeeb]

Of course, just think it should be really low on priority list, if we bother keeping it at all.

[NathanW2]

Yeah just keeping it here to keep the idea in mind. Might be a good plugin idea. On Sep 30, 2014 6:28 PM, "Ben Zeeb" [email protected] wrote:

Of course, just think it should be really low on priority list, if we bother keeping it at all.

— Reply to this email directly or view it on GitHub https://github.com/DMS-Aus/Roam/issues/137#issuecomment-57282082.

[bzeeb]

Speaking of which, as I'm just going through tidying up tickets, should I add a plugin milestone? Basically signify we don't plan on adding it as core but would fit nice as a plugin.

[NathanW2]

Yes On Sep 30, 2014 6:33 PM, "Ben Zeeb" [email protected] wrote:

Speaking of which, as I'm just going through tidying up tickets, should I add a plugin tag? Basically signify we don't plan on adding it as core but would fit nice as a plugin.

— Reply to this email directly or view it on GitHub https://github.com/DMS-Aus/Roam/issues/137#issuecomment-57282538.