Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Archivematica job detail messages are not visible in the Enduro UI #954

Open
fiver-watson opened this issue Jun 4, 2024 · 2 comments

Comments

@fiver-watson
Copy link
Contributor

Describe the issue

Currently, there is no way to see AM STDOUT and/or STDERR messages related to specific jobs run in Archivematica. This can make troubleshooting more difficult and provides operators with less insight into what actions are being performed on their content.

Expected behavior

Currently, Enduro workflow tasks are organized into a table, with a Notes column. At present, that Notes column is not being used.

For now, the initial implementation proposal is to add a "View" link to the Notes column. When clicked, this should open an expandable dropdown below the current row, that will include the STDOUT or STDERR messages from the related Archivematica job.

Screenshots

A rough wireframe has been prepared below:

Enduro-AM-Notes-mockup-v0 1

You can see a bit more context on the following Miro board:

Ideally, much like in AM, STDERR messages would be in a light red frame, rather than the light grey of the STDOUT as shown in the wireframe.

Additional context

This issue is part of an incremental effort to improve the end user messages shown in workflow tasks. Part 1, hiding some of the unnecessary AM tasks, is described in issue #950. Future tickets will also be filed to customize the task names and outcome messages shown in Enduro, for better clarity to operators.

@jraddaoui
Copy link
Collaborator

We should be careful about accessibility, I'm not sure how that expandable section inside a table (inside another expandable section) will work in that regard.

@aseles13
Copy link

aseles13 commented Jun 5, 2024

I am not sure how much work or analysis is still needed to be able to include this in PoC#2, but if we can show them some error messages (user or system) it would be a good step forward.

@sallain sallain added the analysis The action on this issue is to provide analysis label Jun 19, 2024
@sallain sallain removed analysis The action on this issue is to provide analysis SFA POC #2 labels Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 👍 Ready
Development

No branches or pull requests

4 participants