Make ingest Webform Workflow simpler and natural about webform_strawberryfield HOT 9 OPEN

To get the conversation started w/r/t to the first item here: I think a change that could significantly improve the ingest workflow is what you stated last: making the functionality of the buttons more explicit to inform the user exactly what the button(s) is/are doing. Something like "Save Metadata" vs. "Save Digital Object" (the first persists all the metadata and the latter uploads the object into the repository).

from webform_strawberryfield.

@DiegoPino Sorry in advance for this note, a little bit more general about webform and ingesting.
I was talking few minutes ago with Anna about this and my first question was: do we really need a so complex webform for ingesting? Anna answered me absolutely yes! Why?
Well, we have to consider two mainly needs: Cultural Heritage and Institutional Repositories.
The last one is the reason for “user ready” webforms because Horizon2020 requires institutions load publications onto an IR before any other private/public editors, so institution’s researchers are to be able to independently load/ingesting own documents onto Archipelago by a friendly/simple/clear webforms. Maybe we need a second step where Librarian check/edit and approve what user done before make it public/restricted available.
Regarding Cultural Heritage Preservation, which is more my focus, we have a different workflow. In this case the main actors are System Manager, Librarian and Digitization Staff. The first one manage files ingesting by batch scripts or something like IMI while Librarian load/edit metadata by electronic sheet or IMI, so for this kind of use webforms are not so important.

from webform_strawberryfield.

@giancarlobi Thanks for these cases, it is good to remember that batch ingest means Webform use will be for other, specific cases. Your example strikes me because our most recent Archipelago deployment provided a similar workflow (on a much smaller scale!!) - user-entered webform content goes to approval by curator/Librarian. Thinking about these stages can help us. For example the Draft/Published Node Save button is strange now, appearing on multiple wizard pages.

This is a hard issue because descriptive metadata holds almost anything (good thing!), there is no inherent UI coherence about how to interact.

More soon after talks tomorrow with Diego and Mitchell.

from webform_strawberryfield.

One analogy discussed was something like a "Save Progress" button when using a wizard for an ingest workflow. This allows a user to enter as much information about an object or collection, reach a "stopping" point, Save Progress, then return when they have more time, etc. to fully Save or Complete their ingest.

from webform_strawberryfield.

Webform (elements) has Markup elements. Those serve as ways of outputting data/design/info without expecting people to add anything. The Webform docs are quite good (best ones i have seen in Drupal https://www.drupal.org/docs/8/modules/webform/webform-features#s-elements

from webform_strawberryfield.

(Moving my note here since it's directly related to making webform workflow more helpful and not so much related to the topic of issue #41 )
@DiegoPino @giancarlobi, continuing off the third "•" in this comment from issue #41

Perhaps a simple way we could make the "Descriptive Metadata" Webform more helpful / useful / intuitive would be by directly employing the Drupal Help boxes to sort of guide users through where they can go to make modifications and/or provide short explanations for more context on what is happening inside the webform. Since "Descriptive Metadata" is the demo Webform that ships default, by nature, we sort of have to have a very vanilla Webform that almost imposes certain use cases. Fortunately for this project we do have some use cases where people want to really open up the Archipelago box, ignore the vanilla webform and move things around before getting started. Though, it seems we've run into more instances of users wanting to sort of know how everything is working (in other words, "upload and go") before they start tugging on patch cables and wires.

from webform_strawberryfield.

@mitchellkeaney my fear is we could end putting videos/help boxes for things that will be/could be customized. If people, e.g change some fields, the help boxes will still be around and not match. But! Webform has also non input elements. What if you write/bring that help into the webform itself?

from webform_strawberryfield.

dang, did not even think about the help boxes staying static, haha... 🤦
Can you give me an example of non-input elements in the webform, I'm sure what you mean by that?
But ultimately, yes - I can write up these help suggestions to be added in one way or another!

from webform_strawberryfield.

perfect, thank you for linking this!

from webform_strawberryfield.