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.

Sign up for GitHub

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

Jump to bottom

Files not properly processed: At submission the file goes into "Committed" without passing through the editorial board #305

Open
45 tasks done
hermaion opened this issue Nov 12, 2021 · 4 comments
Open
45 tasks done

Files not properly processed: At submission the file goes into "Committed" without passing through the editorial board #305

hermaion opened this issue Nov 12, 2021 · 4 comments
Assignees
@ryanfb

Comments

@hermaion
Copy link

hermaion commented Nov 12, 2021 •
edited by ryanfb

This looks like older issues (#56, #60, #62). I edit existing files and submit them to the DCLP editorial board, but they go into my "committed" section without reaching the appropriate board.

Here follows a list (quite long because I noticed the problem too late) of the affected files, which should be pushed to the DCLP editorial board (https://papyri.info/editor/user/board_dashboard?board_id=60).

Also, would it be possible to find a way to avoid this behaviour in the next submissions?
@ryanfb ryanfb self-assigned this Nov 12, 2021
@ryanfb
Copy link
Member

ryanfb commented Mar 14, 2022

Apologies for the bug and the delay in getting these fixed. Looking through these, it looks like the bug was possibly the result of a temporary git issue which has since been resolved. I also looked through for additional affected publications and only found one not on this list (105874, which I've also fixed), so I don't think it's still happening. However, if it happens again, please let me know!

@ryanfb ryanfb closed this as completed Mar 14, 2022
@hermaion
Copy link
Author

Apologies for the bug and the delay in getting these fixed. Looking through these, it looks like the bug was possibly the result of a temporary git issue which has since been resolved. I also looked through for additional affected publications and only found one not on this list (105874, which I've also fixed), so I don't think it's still happening. However, if it happens again, please let me know!

Thanks a lot! Sorry to re-open this, but it happened again with https://papyri.info/editor/publications/106274 (just edited and submitted, it went to committed) :-(

@ryanfb ryanfb reopened this Mar 25, 2022
@ryanfb
Copy link
Member

ryanfb commented Mar 25, 2022

No worries - I'll take a look, and see if I can find out what exactly is still causing this issue to occur.

@hermaion
Copy link
Author

Thanks! If this may help: they all were files originally encoded in litpap.info without editorial process and then flowed to papyri.info from there.

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

@ryanfb ryanfb

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ryanfb @hermaion