Difference between revisions of "Delete a term"

From ICA-AtoM
Jump to navigation Jump to search
(New page: <span class="pageTitle">Delete an existing term from a taxonomy</span> Main Page > (UM) User manual > UM-3 Add / edit content > [[UM-3.5|UM-3.5 Edit taxonomie...)
 
Line 20: Line 20:
  
  
5. ICA-AtoM displays the [[Term|term]] in [[Edit mode|edit mode]]. ([[Edit screen]]).Click the [[Delete button]].
+
5. ICA-AtoM displays the [[Term|term]] in [[Edit mode|edit mode]] ([[Edit screen]]). Click the [[Delete button]].
  
  

Revision as of 14:53, 13 June 2008

Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.

Delete an existing term from a taxonomy

Main Page > (UM) User manual > UM-3 Add / edit content > UM-3.5 Edit taxonomies (terms) > UM-3.5.3 Delete an existing term from a taxonomy

Open a taxonomy and click the term to delete
Delete the term


1. Click the Add / edit > Term tab on the Main menu bar.


2. ICA-AtoM takes you to the List taxonomy terms screen showing all existing taxonomies.


3. Click the taxonomy you want to edit to expand it and view the terms associated with it.


4. Click the term you want to delete from the taxonomy (locked terms cannot be deleted).


5. ICA-AtoM displays the term in edit mode (Edit screen). Click the Delete button.


6. ICA-AtoM prompts you to confirm the delete request; click "OK".


7. ICA-AtoM deletes the record and returns you to the List screen.


8. Note that you cannot delete a term that has been used as a value in another record. Attempting to do so will generate an error message.

  • E.g. you try to delete "Sub-fonds" from the Levels of description taxonomy, but you get an error message; this means that one or more archival descriptions has "Sub-fonds" as the value in the Level of description field.
  • As of the current version of ICA-AtoM (v1.0 beta), the delete error message is not very informative and only indicates that an error has occurred but not which error or why; this will be addressed in a future release (post-1.0).