Dashboard feedback about datascribe-module HOT 14 CLOSED

The branch should be updated to use the Zend namespace, as well as list all projects alphabetically and with a creator column.

from datascribe-module.

The testing instance is now on this branch.

from datascribe-module.

I notice you switched to using the Laminas namespace. We're going to keep using the Zend namespace until after we release Omeka S 3.0. You're going to need to switch it back.

To be clear, DataScribe only updates a project's modified date-time when a user saves the project form, not any time something happens within the project - e.g. when an item is submitted for review or a new record is created. I see the usefulness of a list of projects on the dashboard, but specifying them as "recently modified" may lead to misunderstandings. Here I think we can safely have a list of all projects ordered alphabetically by name.

from datascribe-module.

Take with a grain of salt, but I prefer:

• Unlocked items: New, In progress
• My items: New, In progress
• Items needing review: All, Needs my re-review

I like the idea of pulling actions out as buttons. We should do it for the dataset show page: Edit project, Add new dataset. That leaves the dataset show page the only one with an actions dropdown. Is there a way to pull those out too? Not sure about that.

from datascribe-module.

I like the consistency in your filter order. Looks good to me.

I also think it's okay to have only the dataset show page be the only page with the actions dropdown, as it has many that are hard to condense. One idea for it, though: we could pull out the most commonly used action, and leave the others in a "More actions" or "..." dropdown.

from datascribe-module.

I really like the idea of pulling out "Edit dataset" and leaving the rest under a "More actions" dropdown.

from datascribe-module.

Am I right in understanding that only projects which are 'public' show up in the All Projects display?

from datascribe-module.

In case anyone was wondering what it looks like for a transcriber (not global admin):

from datascribe-module.

All users should be able to see all public projects. Only global admins and site admins should be able to see private projects to which they don't belong. So, for example, a researcher, author, or editor who is not assigned to a private project should not be able to see that project. This all applies to datasets as well.

from datascribe-module.

I'm not seeing private projects (to which I do not belong) in the all projects dashboard view; I do see them when I go to the Browse Projects. (logged in as me, not as transcriber user)

from datascribe-module.

@mebrett I forgot to ask whether the newest change fixed the above problem. Did it?

from datascribe-module.

I'm still only seeing public projects in the All Projects on the dashboard. I do see al projects when I go to browse

from datascribe-module.

A question about the distinction between "new" and "in progress" items on the dashboard. For "my items," it appears that items with records show up as "in progress," which makes sense. For unlocked items, there are two items in the "Paulist Mission Chronicles" dataset which have media but no items. I would expect those to show up under "new," but they show up under "in progress." Is that expected?

from datascribe-module.

Ah, the "new" and "in progress" filter strings were switched. It should be fixed now. Thanks for finding the bug.

from datascribe-module.