Rename problem
Edelweiss opened this issue · comments
YTBD
- new view with text field for dclp hybrid (new file name, new dclp-hybrid name (optional), dummy header) ok
- set dclp-hybrid ok
set dummy header / reprint (update header, dummy header as in ddb)- implement similar functionality for DCLP Text Identifier as well (vote?, rename!) ok
- rename text/meta relatives as well ok
@rla2118 in an e-mail
I chose to do TM 372062, http://www.litpap.info/editor/publications/1051, and I can report the following about my attempt: […] it would not finalize (I was, however, able to vote and rename it). Instead of getting the error message about conflicting names, I received the standard “We’re sorry, but something went wrong” notification.
new problems
- won’t finalize ok [repository problem]
- timestamp in publication title / broken publication title after rename (only sometimes)
- rename publication title if dclp-hybrid is given [no, this is no standard behaviour]
problems that still need to be solved:
- timestamp in publication title / broken publication title after rename (happens after »finalize« and propagates back to parent publications within the board’s hierarchy)
publication titles before »finalize«
1|SoSOL;2018;0001|1|User|submitted/2018/02/08/SoSOL;2018;0001|submitted|1|User||
3|Elemmire/SoSOL;2018;0001|1|Board|approved/2018/02/08/SoSOL;2018;0001|approved|1|User|1|
5|DCLP_Editorial_Board/Elemmire/SoSOL;2018;0001|1|User|DCLP_Editorial_Board/finalizing/2018/02/08/SoSOL;2018;0001|finalizing|1|User|3|
publications titles after »finalize«
1|SoSOL;2018;0001|1|User|committed/2018/02/08/SoSOL;2018;0001|committed|1|User||
3|Elemmire/SoSOL;2018;0001 (2018/02/08-14.56.01)|1|Board|archived/2018/02/08/SoSOL;2018;0001|archived|1|User|1|
5|DCLP_Editorial_Board/Elemmire/SoSOL;2018;0001 (2018/02/08-14.56.01)|1|User|DCLP_Editorial_Board/finalized/2018/02/08/SoSOL;2018;0001|finalized|1|User|3|
Elemmire/SoSOL;2018;0001
becomes
Elemmire/SoSOL;2018;0001 (2018/02/08-14.56.01)
However, at the same time the entry disappears from the board’s dashboard. This seems to be normal behaviour when a publication is moved from status »approved/finalizing« to status »archived/finalized«. (It doesn’t propagate forwards, i.e. not to the publications for secondary boards, such as translation.)
Cannot reproduce error, but I’m sure it exists…