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: 5/15/2017    dbserv v1 (albuquery) is integrated with metaserv v1. As a consequence, column metadata are returned with with the data in the metadata section of the result.    As a part of this ticket, dbserv v1 and metaserv v1 were tested and debugged, tickets were created for outstanding issues, and SUIT code was updated.     * Consolidate PDAC table information, used by SUIT in LSSTMetaInfo.json on the server side. In the future this file might be converted to a table and stored in metaserv under SUIT curation. To facilitate development, we'd like to store it as a resource with the source code.   * Update SUIT code to work with dbserv v1 (albuquery) and metaserv v1  a. Query metaserv to create table constraints table  b. Use column metadata returned by dbserv for data definition info, such as units and description    XW (12/21/2016)   We will be using MetaServ to get the database names, data types served, table names, and other information.    09/18/2017 (<USER>    The information provided by the current [metaserv prototype]([http://lsst-qserv-dax01.ncsa.illinois.edu:5005/meta/v1/db/]) is not yet sufficient to automate search interface creation. There is an ongoing discussion with DAX team on which information is missing. See    [https://confluence.lsstcorp.org/display/DM/Data+Access+meeting+2017-09-11]    At the moment, it is not clear how to replace the information in [LSSTMetaInfo.json]([https://github.com/Caltech-IPAC/firefly/blob/dev/src/firefly/java/edu/caltech/ipac/firefly/resources/LSSTMetaInfo.json]) (used by SUIT to support PDAC) with the information from metaserv.    The current implementation is sufficient to get column name, datatype, unit, description, if we'd like to descope the use of metaserv just for this purpose.    Metaserv prototype:   [http://lsst-qserv-dax01.ncsa.illinois.edu:5005/meta/v1/db]    Metaserv documentation:   [http://dm.lsst.org/dax_metaserv/api.html]    Table definitions in the available database schema:   [http://lsst-qserv-dax01.ncsa.illinois.edu:5005/meta/v1/db/W13_sdss/sdss_stripe82_00/tables/]    Dump of column definitions:   [https://gist.github.com/brianv0/e6cfc4ba36ced2a57eb131210ba16c46#file-dump-yaml-L34]    _______________________________________    This ticket list two issues to be considered later:   * The test version of the two search processors had hard coded database's name. But there will be multiple databases, we need to find a better way to handle it. Should it be passed to the server side or should it be stored in a configuration file? Currently, if the database name is not defined in the property, the hard coded default name is used.  {code} //private static final String DATABASE_NAME =AppProperties.getProperty("lsst.database" , "<USER>sdss_stripe92_patch366_0");   private static final String DATABASE_NAME =AppProperties.getProperty("lsst.database" , "");  {code}     * When the DAX server is down, it takes a long time to return a failed message back. To avoid confusing the users, the timeout control is set in in the getDataToFileUsingPost of the URLDownload class. The default value is 30seconds. The timeout field may be stored in the property file later.  {code}             URLConnection c = makeConnection(url, cookies, requestHeader, false);               c.setConnectTimeout(timeout * 1000);//Sets a specified timeout value, in milliseconds               c.setReadTimeout(timeout * 1000);  {code}
Answer: 809136.0