give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Once we have the new service deployed we need to migrate the data from the current production database {{squash-db}} to the new QC Tier 0 database schema implemented in DM-12193    The task consists in grabbing the jobs from the current production API https://squash-api.lsst.codes/jobs/<id>, convert them to the new verification job format and use the new API https://squash-restful-api-demo.lsst.codes/job to restore these jobs.    The result should be an script that helps us to automate that task, so that we can repeat it easily and restore the current production database.    Assuming that the current production API provides all the data we need, i.e if  no change in the API is required, the real work is to write the piece of code that converts the jobs to the new verification job format.    This [notebook|https://github.com/lsst-sqre/squash-rest-api/blob/master/tests/test_api.ipynb] provides and example on how to use the new API and POST verification jobs.    Transformation from the old job format to the verification job format.     You can check the new format of the verification jobs in the above notebook. It has:    {code:java}  data.keys()  dict_keys(['metrics', 'measurements', 'meta', 'blobs', 'specs'])  {code}    you don't have to worry about {{'metrics'}} and {{'specs'}} this info will not be restored. It is completely different in the new format, the only thing we need is to the {{metric}} name right which is the key for the metrics definition and specifications.    1) {{data['measurements']}}    OLD FORMAT:    {code:java}  { "metric": "PA1",    "value": 14.9064428565398,    "metadata": null}  {code}     NEW FORMAT:    {code:java}    {'blob_refs': ['42ddf00268f244748d33f6dbae219371',     'e92c8be5a34c45d1aaad00d5913d27c9',     'd34a77ba0b234f6b95dc88cfccacccc6',     '39e2da347ae84d01aa369f5f4f23d9ef'],    'identifier': 'd35daa0952294deda56d4adcac6ca06c',    'metric': 'validate_drp.AF3_stretch',    'unit': '%',    'value': 1.35345435345}    {code}    1.1) Now metrics are prefixed by the verification package, all metrics in production are for the {{validade_drp}} package so you have to rename the metric name to {{validate_drp.<metric>}}    1.2) Include {{unit}} field, its value can be discovered from the https://squash-api-dev.lsst.codes/metrics/<metric name>    1.3) I dont use the {{identifier}} field, so you can include and left its value {{null}}    1.4) include {{blob_refs}} field, the list of blob {{identifiers}} can be obtained from   {code:java}  data['measurements']['metadata']['blobs']  {code}  or let it {{null}} if there's no blob associated to the job. Note that {{blob_refs}} is just a list in the new format.    OLD FORMAT:  {code:java}  "measurements": [          {              "metric": "AM1",              "value": 10.7817351689061,              "metadata": "{'blobs': {'astromModel': 'fb1a324139da49b99c8383c5837ae862', 'photomModel': '63e56a6c8a9a4ae398d4ee69caeec748', 'matchedDataset': '77cfbfdc61ad4d19a8fee7cf468edbae'}  {code}    2) {{data['blobs']}}    Blobs format has not changed, they always have the following keys:    {code:java}  data['blobs'][0].keys()  dict_keys(['identifier', 'data', 'name'])  {code}    However,  the {{extras}} and  {{parameters}} fields in the old format:    {code:java}  measurements['metadata']['extras']  measurements['metadata']['parameteres']  {code}     became a single blob in the new format. So you have to merge {{extras}} and {{parameters}} into a single object that goes into the {{data}} key in     {code:java}  data['blobs'][0].keys()  dict_keys(['identifier', 'data', 'name'])  {code}    you have to generate a new blob UUID-4 based  identifier using       {code:java}  import uuid  identifier = uuid.uuid4().hex  {code}    Finally the blob name is the name of the associated metric (see 1.1) above.    The new blob must be added to the data['blobs'] list and its identifier added to the {{blob_refs}} for this measurement (see 1.4 above).     Example of data['blobs'] in the new format is available in the notebook mentioned above.    3) {{data['meta']}}    These fields in the OLD FORMAT:    {code:java}  "ci_id": "1085",  "ci_name": "validate_drp",  "ci_dataset": "hsc",  "ci_label": "centos-7",  "date": "2017-10-13T11:58:30Z",  "ci_url": "https://ci.lsst.codes/job/sqre/job/validate_drp/dataset=hsc,label=centos-7,python=py3/1085/",  "status": 0,  {code}    now go to:    {code:java}   data['meta']['env']  {code}    You have to add a new field, though    {code:java}  data['meta']['env']['env_name'] = 'jenkins'    {code}    with the fixed value {{jenkins}} for all jobs.    {{packages}} are now part of metadata in the NEW FORMAT:    {code:java}   data['meta']['packages']  {code}    but the {{name}} field also became a key:    {code:java}    { 'apr': {'eups_version': '1.5.2',    'git_branch': None,    'git_sha': '39b3212aa46217e4f485b02496381907da8b8d7a',    'git_url': 'https://github.com/lsst/apr.git',    'name': 'apr'},    'apr_util': {'eups_version': '1.5.4',    'git_branch': None,    'git_sha': '45d74ccc249484be4fdba93fe2f66aafb5869335',    'git_url': 'https://github.com/lsst/apr_util.git',    'name': 'apr_util'}, ... }      {code}  we should preserve the value of the 'date' field which corresponds to the timestamp when the job was originally created.  
Answer: 125476.0