-
Notifications
You must be signed in to change notification settings - Fork 7
Configuring Tech Check 2 Card Config
-
Ensure the Preprint feature flag is on (http://ci.aperta.tech/admin/feature\_flags)
-
Ensure the Card config feature flag is on
-
Create a new Tech Check card (see TechCheck)
-
Create a new Changes for Author card (see EmailTemplate). Use
changes-for-author
as the value for theletter-template
attribute. -
Note down the journal id (e.g. from https://ci.aperta.tech/admin/journals/4/cards the journal id is 4)
-
Note down the card id for the Changes for Author card (e.g. https://ci.aperta.tech/admin/card/63 the card id is 63)
-
Now, we want to automatically create a Changes for Author card when the paper is sent back to the author. We will use the behavior system. Log into the environment you want to use and
cd
ot the tahi directory.$ cd /var/www/tahi/current/ $ bede rake "behavior:create:create_task[6, paper.state_changed.checking, 63, false]"
This indicates that on the change to the
checking
state for papers in Journal 6 we want to create Card 63. The false means that we should not allow duplicate cards, that is, we should only create the card once. -
Next, we want to ensure that the Changes for Author task is marked incomplete when the paper is sent back for checking. Again, log into the environment
$ bede rake "behavior:create:task_completion[6, paper.state_changed.checking, 63, incomplete]"
This indicates that on the change to the
checking
state for papers in Journal 6 we want to mark any tasks that are instances of Card 63 incomplete if they are not already marked incomplete. -
You are finished! You should now have a working card config tech check workflow.