You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For most boards and commissions, it is sufficient to specify the type of file being uploaded and the meeting date associated with the file. In those cases, drupal-module-onboard can automatically assign the link text to the file to make things consistent across all boards and commissions.
However, there are some cases when there are multiple packets and it is useful to be able to disambiguate which packet is which (as an example). In this case, we also provide a title field that can be used to manually specified what should be shown on the web:
Currently users are adding a title and using the field in an inconsistent way. (example)
We should emphasize the the field is optional. We could move it to the end of the form and add a note that the field is optional. We could also add help text: "Titles are optional. Manual titles are useful when associating multiple files of the same type with one meeting. The meeting date should not be included with the title"
We may also want to consider automatically pre-pending the type to a title.
Or maybe we only want to show the title when there is more than one file of the same type.
The text was updated successfully, but these errors were encountered:
For most boards and commissions, it is sufficient to specify the type of file being uploaded and the meeting date associated with the file. In those cases, drupal-module-onboard can automatically assign the link text to the file to make things consistent across all boards and commissions.
However, there are some cases when there are multiple packets and it is useful to be able to disambiguate which packet is which (as an example). In this case, we also provide a title field that can be used to manually specified what should be shown on the web:
Currently users are adding a title and using the field in an inconsistent way. (example)
We should emphasize the the field is optional. We could move it to the end of the form and add a note that the field is optional. We could also add help text: "Titles are optional. Manual titles are useful when associating multiple files of the same type with one meeting. The meeting date should not be included with the title"
We may also want to consider automatically pre-pending the type to a title.
Or maybe we only want to show the title when there is more than one file of the same type.
The text was updated successfully, but these errors were encountered: