From f54ebb3d5a0c2688ef337392eb3775dceda42398 Mon Sep 17 00:00:00 2001 From: Gael Yvert <Gael.Yvert@ens-lyon.fr> Date: Fri, 16 Dec 2022 16:42:02 +0100 Subject: [PATCH] more admin doc --- doc/admin/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/admin/README.md b/doc/admin/README.md index 9ee2997..725a57e 100755 --- a/doc/admin/README.md +++ b/doc/admin/README.md @@ -302,9 +302,9 @@ They correspond to pieces of information that are linked to stocks. Each type of | Created At | Timestamp | Timestamp of the record update in the database | | Color | Character string | The color with which the feature will be displayed on plasmid maps. Do **NOT** edit directly because your color name or syntax may not be recognized properly. Instead, select one of those proposed by the dropdown menu | -After adding or editing DNA features entries, your **modifications will NOT directly appear on the plasmid maps** unless you directly **UPDATE PLASMID MAPS WITH THE LATEST FEATURES**. Technically, this corresponds to updating the BLAST database containing the DNA features sequences. To achieve this update, go to the `browse` page of the `DNA features` and click on the blue button (top right) labeled `Update Plasmid Maps with these Features`. +After adding or editing DNA features entries, your **modifications will NOT directly appear on the plasmid maps** unless you intentionally **update plasmid maps with the latest features**. Technically, this corresponds to updating the BLAST database containing the DNA features sequences. To achieve this update, go to the `browse` page of the `DNA features` and click on the blue button (top right) labeled `Update Plasmid Maps with these Features`. -Now your latest changes should appear on the plasmid maps. +Now your latest changes should appear on the [plasmid maps](#Plasmidmaps). *[Back to Contents](#Contents)* -- GitLab