feature creep

[romanchyla]

master pipeline was designed to update solr; later on metrics db was added - but it's sort of 'artificial' connection and the api reflects this 'growing' unease

the central application object has 'update_storage' and 'delete_by_bibcode' methods; those methods only touch the local storage; there exist separate methods for updaitng solr/metrics

a much cleaner api would probably only expose one 'update/delete' method. internally there would be a set of targets, each conforming to a defined api (solr, metrics db....) which would be modified by the application.

another symptom of malaise is that tasks now have to call three methods in order to update a record; see task_delete_record