Page History

...

•  flag, and do not follow-thru with, any title whose instance has been modified since it was first created - for each of these...
  •  update the MARC so that it agrees with the instance and then follow-thru with...
•  add an 856 like so: $uhttps://walter.drew.edu/cgi-bin/folio/editMARC/{instanceId}$yeditMARC replace Sirsi-based 999s with FOLIO-based 999s
•  overlay (PUT) FOLIO's instance db table - this is because several 7xxs were added to the wrong instances - overlaying the instance will correct those mistakes
•  add (POST) the new MARC to FOLIO's "records" db table
•  add (INSERT) the instanceId, recordId, mrc, and solrID to the folio.titles MySQL db table
•  overlay (UPDATE) Walter's MySQL db with the new MARC and re-index in Solr
  
  •  
  add (POST) the new MARC to FOLIO's "records" db table
  • delete the Sirsi CatalogKey solrID and add the 001 solrID

But all of that is going to take time and so here's the plan:

1. set up a page process on Walter that will enable us to add or edit titles and update both instances and records while keeping Walter's Solr index up-to-dateadd records for all of the instances that currently have items checked out in the loans db table
   
   1. search MySQL::folio.titles for the instanceId instanceIds to determine whether of not there is a recordId
      
      1. if yes: consider the next instanceIdif no...
      2. PUT the instance to correct eroneous 7xxs unless the instance has been modified in which case make a note of the 001
      3. POST the record
      there is : ignore it
      4. if there is not >>instanceIds2process.txt
   2. PUT each instance
   3. POST each record & update Solr
2. send that questionnaire back to EBSCO and get Patron Functionality off the ground
3. load records for the rest of the recordLess instancesload instances and records for all Louisa titles  
4. make bibServices work for batches as well as individual titles