Guided workflows in HDV production to ensure users deposit into proper workflows (Journals, collections, root)

[sbarbosadataverse]

Slack thread: https://iqss.slack.com/archives/C08EF68QSSV/p1775055787448759

How far away are we from being able to guide users when they start production? For example, all these misplaced datasets that should go into journal collections?
Like a pop-up saying :

Is this submission for a journal? Yes? Here is a list of journals with collections in the repository
Will you deposit more than 1 dataset over time? Yes? Go directly to create a collection
Will you never come back after this one deposit? Here, deposit in the root.

Just wondering how difficult this would be, but would still like to think about how we design something like this to continue improving guidance over time. I don't want this to be a cut-and-paste of disconnected improvements to guidance.

[sbarbosadataverse]

@scolapasta

Gustavo wrote:
I wonder if this is a pop-up that should be configurable when you create a dataset at any Dataverse collection (*).

a) I can imagine any collection may want some kind of pre create dataet messaging.
b) Generally, we want to limit special rules for the root collection, and treat it as any collection. This becomes even more important as we continue to support consortium models, where they’re top level collections can play a similar role to the installation root collection for each individual member in the consortium.

(*) of course, getting a pop-up each time you click create on a dataset (in a collection) could be a little annoying to users. That said, for our use case, we know the message is in root where users should generally not be creating a lot of datasets. So maybe it’s fine. We could consider having a “don’t show again checkbox” but we’d have to store it for each collection / message. And what if the message changes, then do we auto clear those checks (probably).
Alterrnatively we could not show the message of you have a certain permission. Not sure I like this idea, nor am I sure what permission we would check for. But just brainstorming here, for now.

Happy to add these comments to an issue, if you creat one @Sonia Barbosa.