diff --git a/content/coll_manager/images/batch/_index.en.md b/content/coll_manager/images/batch/_index.en.md
index 046fad6c..1eff2bb8 100644
--- a/content/coll_manager/images/batch/_index.en.md
+++ b/content/coll_manager/images/batch/_index.en.md
@@ -1,6 +1,7 @@
 ---
 title: "Batch Uploading/Linking Images"
 date: 2021-10-06
+modified: 2023-10-17
 weight: 1
 authors: ["Ed Gilbert","Katie Pearson"]
 keywords: ["images"]
@@ -23,5 +24,3 @@ There are several workflows used to batch upload/link specimen images. Batch pro
 
 * **Remote Image Storage:** Images can also be processed and stored on a remote server and mapped to the specimen image through the full image URL. Standalone image processing scripts will be needed to process images and map image URLs to the portal database. Scripts can be configured to write the image URL directly to the database or image metadata can be written to a log file, which is loaded into the database afterwards. Remote images must be mapped into the database using the full image URL with the domain name.
   * If only a large image is made available from the remote server, the image URL can be mapped to the _urloriginal_ field, and then portal will then create local web and thumbnail dirivatives. If the images are named using the catalog number, and the web server is configured to display directory contents, the Processing Toolbox within the collection's management menu contains a method to harvest image links from the directory listing. Alternatively, one can perform a "skeletal record import" that contains a column with the catalogNumber and another associatedMedia column with the image URL.
-
-* **CyVerse Image Storage:** This method requires an agreement of a collection with CyVerse. CyVerse can store images as Community Data files and use BisQue to create web-accessible URLs for these files. You can then use the Processing Toolbox to map CyVerse URLs to specimen records in your portal.