Removing Content

From UA Libraries Digital Services Planning and Documentation
Revision as of 15:20, 9 January 2015 by Jmanderson (talk | contribs) (Created page with "The process to do this is as follows: First, check to see if the content is in LOCKSS: log into the database InfoTrack, select * from inLOCKSS where id_2009 like “u...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The process to do this is as follows:

First, check to see if the content is in LOCKSS:

       log into the database InfoTrack, select * from inLOCKSS where id_2009 like “u0003_0003696”;
          if null, then we can delete content in the archive.  
          If it’s in there, though, we create a problems.txt in the Documentation folder in the archive and say what happened.) 

If NOT in LOCKSS:

     If any items are in the collection, we cannot delete the directories!   In that case, ASK DONNELLY IF THE ITEMS NEED TO GO TO THE OTHER COLLECTION, and:  

`rm /srv/archive/u0003/0003696/Metadata/*ead*xml’ (this gets versioned ones as well) `rm /srv/www/htdocs/content/u0003/0003696/Metadata/*ead.xml’ Modify the manifest to remove EAD links: vi /srv/archive/u0003/0003696/Documentation/Manifest.html

      If NO items are in the collection, make a note of the title for the next set of steps, and then:

`rm –r /srv/archive/u0003/0003696` `rm –r /srv/www/htdocs/content/u0003/0003696`; And remove from database: delete from allColls where id_2009 like “u0003_0003696” And remove the flat file for checksums: rm /srv/scripts/md5/cya/checksums/u0003/0003696

     In either case, remove the EAD listing from the database:  delete from allColls where id_2009 like “u0003_0003748” and AnalogOrDigital like “A”;

If in LOCKSS:

    Create a problems.txt in /srv/archive/u0003/0003696 and indicate that Donnelly told us on x date to take the EAD down, that it was combined with collection u0003_0003748
    Remove the live version:
    If there’s items: 
            `rm /srv/www/htdocs/content/u0003/0003696/Metadata/*ead.xml’   -- AND ASK DONNELLY IF THE ITEMS NEED TO GO TO THE OTHER COLLECTION
             
    If no items: `rm –r /srv/www/htdocs/content/u0003/0003696`;
                    In either case, update database so it won’t show in the browse listing, and so we know what happened:
                                 update allColls set online=”NULL”, inAcumen=”NULL, listLevel=”NULL, notes = “MSS 3696 Guide to the Arley E. Hughes Sr. Letters was added to collection MSS 3748 on 7/21/14 per Donnelly Lancaster, then taken offline” where id_2009 like “u0003_0003748” and AnalogOrDigital like “A”;
               

Whether in LOCKSS or not, remove alternative versions of the EAD: `rm /srv/deposits/EADs/*/u0003_0003696.ead.xml`


SECOND, since this impacted another collection, check the title both in the database and in the Manifest in the archive (and the collection xml). view /srv/archive/u0003/0003748/Documentation/u0003_0003748.xml (there is none, since there’s no items online yet). vi /srv/archive/u0003/0003748/Documentation/Manifest.html (changed the title to “Hughes family papers” on both <head> and <title> lines. In the InfoTrack database: select * from allColls where id_2009 like "u0003_0003748"; (the title was in this case updated by the upload of the new EAD; if it was not, must modify it. ) Also in this database, add a note: update allColls set notes = “MSS 3696 Guide to the Arley E. Hughes Sr. Letters was added into this collection 7/21/14 per Donnelly Lancaster; that collection was removed.” where id_2009 like “u0003_0003748”;


THIRD: If the collection for which an EAD was retracted contains items, check to see if the items go to another collection. If they do, that’s a whole ‘nother process, that impacts checksums too…