Some Plomino terms are confusing

[djay]

user problem

When training users I notice many terms in plomino make it harder to undrleedtand than it could be.

Form - when replacing paper forms users get confused between the filled in form (document) and the empty form. They use them interchangeably. In addition plomino allows for multiple forms to be used with the same document which doesnt work when you consider a paper form as an analogy. Form is generally an overloaded term.

Document - end users think of word documents not data or records. In some cases I've seen users use the word "Form" to mean saved form data.

View - overloaded in plone and doesnt make much sense to the end user.

Database - when a user of plone comes to work with plomino they aren't thinking of it as a database mostly. They are thinking they want to create a survey or contact form or small application or workflow of some kind of form etc.

options

Form -> Layout

Database -> Service

View -> List (report? Listing?)

Document -> Record?

e.g.

1. User opens a plone folder and selects "Add new" > "service".
2. User seems IDE. Clicks "Add new" > "Layout".
3. Layout editor is open. User drags "Text field" onto layout editor.
4. User clicks on "Layout settings" to edit id and title of Layout.

[djay]

@ebrehault So I think we decided "Plomino Database" becomes "Service". What about the others?

Form -> Layout is perhaps more controversial.

[ebrehault]

What about "mask"? (that's actually the french term for Lotus Domino forms, "masque")
In a way, a form is a way to disguise a document.

[djay]

@ebrehault mask is technically closer to the actual idea but I'm not sure works well in english.
Still thinking Form Layout.
So no issue renaming Document to Record?

[ebrehault]

Fine with me.