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

Author/work stable identifiers being erased in DCLP editor #322

Closed
ryanfb opened this issue May 3, 2022 · 1 comment
Closed

Author/work stable identifiers being erased in DCLP editor #322

ryanfb opened this issue May 3, 2022 · 1 comment
Assignees
@ryanfb

Comments

@ryanfb
Copy link
Member

ryanfb commented May 3, 2022 •
edited
Loading

I tested this out last night and again this morning, and things mostly appear ok. But it looks as though there's another bug with author/work stable identifiers: they have been wiped from the records I'm revising. They do not save when entered into the metadata mask, and although I can add them manually to the xml, if I make any further changes to the metadata and save, they get erased again.

Screen Shot 2022-05-03 at 8 45 44 AM

Originally posted by @samosafuz in #320 (comment)
@ryanfb ryanfb self-assigned this May 3, 2022
ryanfb added a commit to sosol/sosol that referenced this issue May 4, 2022
@ryanfb
Add log line for DCLP complement_params (see papyri#322)
55197d1
ryanfb added a commit to sosol/sosol that referenced this issue May 4, 2022
@ryanfb
Try config-level change to fix nested hash in ref (see papyri#322)
b395d7e
ryanfb added a commit to sosol/sosol that referenced this issue May 4, 2022
@ryanfb
Revert "Try config-level change to fix nested hash in ref (see papyri…
07ecf6e 
…#322)"

This reverts commit b395d7e.
ryanfb added a commit to sosol/sosol that referenced this issue May 4, 2022
@ryanfb
Use an array joined into a string for DCLP refList (see papyri#322)
3bf20a0
@ryanfb
Copy link
Member Author

ryanfb commented May 4, 2022

This should now be fixed in production. @samosafuz — let me know if you're still running into any issues. Thanks!

@ryanfb ryanfb closed this as completed May 4, 2022
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
1 participant
@ryanfb