Skip to content

[ORE Submission] Move the location of the Data Availability block in the form #285

Closed

Description

@mreiko

Description
CERN request to move the location of the Data Availability block in the form cc: @1StuJB

  1. Can you also please move the Data Availability block to directly under the Data Citations block on the same page please. It makes more sense to have it here than two pages later on.

Note: Original ticket reported here: #167 (comment)


Development Updates

Pull requests:

Update 27-07-2026 Jarda
ui-library: pkp/ui-library#939
pkp-lib: pkp/pkp-lib#13089

Activity

  1. added theissue type on Jun 29, 2026
  2. mreiko commented on Jun 29, 2026

    @mreiko
    Author

    Can this be accommodated for ORE-only? @jardakotesovec

  3. self-assigned this
    on Jun 29, 2026
  4. changed the title [-][Submission] Move the location of the Data Availability block in the form[/-] [+][ORE Submission] Move the location of the Data Availability block in the form[/+] on Jul 2, 2026
  5. assigned and unassigned on Jul 6, 2026
  6. removed their assignment
    on Jul 9, 2026
  7. mreiko commented on Jul 20, 2026

    @mreiko
    Author

    Waiting for design feedback with @Devika008

  8. mreiko commented on Jul 21, 2026

    @mreiko
    Author

    Design will be complete by tomorrow, will be reviewed, and then handed to dev for implementation.

  9. added a commit that references this issue on Jul 23, 2026
  10. added 2 commits that reference this issue on Jul 23, 2026
  11. 4 remaining items

  12. added 8 commits that reference this issue on Jul 23, 2026
  13. added 2 commits that reference this issue on Jul 23, 2026
  14. Tribunal33 commented on Jul 23, 2026

    @Tribunal33
    Collaborator

    This passes QA. Looks correct. It is now underneath data citations block on Step 2 - Details.

    @blesildaramirez was this a regression? I see that data availability statement is required during the submission and in theory be required in the publication metadata. But I see it isn't and can remove the data availability statement. This might not be part of this ticket. If you think it should be moved to another ticket let me know. I am going to approve this for now and you can close it after you review.

    Image
  15. mreiko commented on Jul 23, 2026

    @mreiko
    Author

    Hi @1StuJB Ready for review on the ORE VM.

  16. blesildaramirez commented on Jul 24, 2026

    @blesildaramirez

    Hi @Tribunal33 , I checked this and it seems this is the expected behavior in 3.5. Also, the label says "Require the author to provide a data availability statement before accepting their submission.", which means required is only for authors on the submission wizard. I also checked the Supporting Agencies, had it set to require for authors, and it was working as required on the submission wizard but became optional in the publication metadata.

    Closing this one.

  17. 1StuJB commented on Jul 27, 2026

    @1StuJB
    Collaborator

    Thanks @mreiko, confirmed and approved completion :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions