udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
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: "The proposed mission statement for the LSST Software Stack development: {quote} Enabling LSST science by creating a well documented, state-of-the-art, high-performance, scalable, multi-camera, open source, O/IR survey data processing and analysis system {quote} with the following rationale:  * well documented -- as otherwise it will be impossible to maintain or be usable for Level 3 * state-of-the-art -- because the quality of the instrument and needs of the science to be systematic limited require us to develop new algorithms an break new ground in a number of areas * high-performance -- because of the massive amount of data we need to process for a reasonable budget * scalable -- because we need it to run from between a single core (for developers, or Level 3 users) to tens of thousands of cores (for Data Release production) * multi-camera -- because we need to process precursor data for development purposes, and because our as-delivered camera won't be ideal. * open source -- because we want the community and future surveys to benefit from our efforts. "
Answer: 512452.0

User story: "Enable C\+\+11 support on all platforms. As far as I know, we're currently blocked on knowing whether the stack builds with libc++ with clang (required for OS X support)."
Answer: 346967.0

User story: "The Data Products review committee has recommended to change what we call 'Source' to something that is less likely to cause confusion (e.g., 'Detection').  This issue captures the need to: * Decide on the new terminology * Perform a massive rename throughout the source code to adopt it."
Answer: 512667.0

User story: "Transition gitolite-managed repositories to Atlassian Stash."
Answer: 512670.0

User story: "To enable seamless interaction with the community, LSST code repositories should be automatically mirrored to github.  Any github user must be able to fork our repositories as necessary and build using the source from github.  They should be able to open github issues, which will be monitored by us and transitioned to Jira as necessary.  They should be able to post pull requests, which we would merge with our code (after proper review and vetting)."
Answer: 295881.0

User story: "As a user, I need to know how to:  * Install EUPS itself * Install new packages * Setup packages * Selectively override a package being setup-ed "
Answer: 767794.0

User story: "Use of the WAVE accessibility assessment tool ([https://wave.webaim.org/]) shows a variety of accessibility concerns in the DuraCloud SyncTool UI. Screenshots from the tool (using the browser extension) are attached to capture the summary numbers.    Further investigation will be needed to determine which of the listed notices need attention.         See suggestions from accessibility reviews in ticket DURACLOUD-1264"
Answer: 210227.0

User story: "This will require alternatives for SES, SNS, SQS, and S3 storage. This will require changes across all DuraCloud baselines."
Answer: 7520.0
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: "As an administrator, I'd like to be able to export a .csv file that includes the name, username, email address, and role of all active users of accounts I administer. "
Answer: 434909.0

User story: "Based on changes in Oracle's licensing model which took effect on April 16, 2019, the Oracle JDK is no longer free to download and use for production applications. See: [https://www.oracle.com/technetwork/java/javase/overview/oracle-jdk-faqs.html]    The approach recommended by Oracle is to transition to the use of OpenJDK. Builds of OpenJDK will be continually available and licensed to allow production use: [https://adoptopenjdk.net|https://adoptopenjdk.net/]    The most current LTS version of OpenJDK is Java 11. This version of Java is also the most consistent with the Oracle SDK, so should be the migration target.    These migration guides may be helpful:    - [https://docs.oracle.com/en/java/javase/11/migrate/index.html]    [- https://blog.codefx.org/java/java-11-migration-guide/|https://blog.codefx.org/java/java-11-migration-guide/]"
Answer: 542730.0

User story: "Users of the Chronopolis storage provider should be able to see statistics indicating:   * The total number of snapshots   * The total number of files across all snapshots   * The total amount of stored content across all snapshots"
Answer: 472597.0

User story: "Due to the fact that CloudwatchStorageStatsGatherer is not pulling sufficiently recent stats it should be removed.  Instead, non-Glacier storage stats should be pulled from the manifest."
Answer: 218.0

User story: "Part of the CANARIE-funded grant project managed by the University of Toronto is to use DuraCloud to connect to the Ontario Council of University Libraries (OCUL)'s Ontario Library Research Cloud (OLRC), which is based on OpenStack Swift storage.    The goal of this ticket is to add a new DuraCloud StorageProvider implementation using the S3 API for Swift."
Answer: 166987.0

User story: "Currently the ManifestWritingTaskProcessor causes downstream processors to be ignored if the manifest has been successfully updated.   This skipping of downstream processors is leading a failure to retry attempts to generate a DuplicationTask on object update (be it create, update or delete).  The work of this task is to stop ignoring downstream tasks when the manifest is unchanged."
Answer: 47.0

User story: "My apologies if this has already been created elsewhere, and please feel free to edit it. We wanted to create a Jira issue to start the discussion about what to do with DPN-related code in Duracloud in light of the recent news."
Answer: 79041.0

User story: "In Duradmin,  create a content item and attempt to add a tag to it.  You should see a javascript error message."
Answer: 67586.0
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: "Expand capabilities of non-root users with secondary storage providers such that they can manage spaces and add content          Texas Digital Library members using the TDL DuraCloud may have different storage providers for different content types. The limitations of current functionality in DuraCloud is such that users interacting with 'secondary' providers cannot add and manage spaces.     If there was a way to toggle on/off between the ability to add and manage spaces in so-called secondary providers, TDL users could more successfully manage different content types in separate DP storage environments (ex. Glacier as primary for repository backup, DPN as primary for ETDs)     "
Answer: 193094.0

User story: "This display would be alongside the root user management display and would provide a way to:  - See a list of all root users - Give a user root privileges - Remove root privileges from a current root user"
Answer: 3866314.0

User story: "Recently there have been two instances reported where a space has been unintentionally deleted while the user was attempting to delete a content item in the space.    We should consider what mechanism would be able to reduce this risk.    We should also consider how we might provide a way to recover from this error. Especially when a secondary provider exists, there is an opportunity to allow a restore action from that secondary store, but only if duplication is deferred."
Answer: 623641.0

User story: "With the completion of DURACLOUD-923, it is now possible to use the Range header to download parts of a large file. This task is to update the Retrieval Tool to use this new feature when retrieving files larger than 100 MB.    The StoreClient may also need to be updated to support Range-based GET requests."
Answer: 290477.0

User story: "This work would replace the existing RTMP-based streaming service provided by DuraCloud with a streaming service which utilizes HLS. RTMP streams require flash-based players, and as flash support in modern browsers has diminished, and flash itself  is on track for EOL (https://theblog.adobe.com/adobe-flash-update/), there is a need to transition DuraCloud's streaming technologies to a more current medium."
Answer: 209960.0

User story: "Downloading bit integrity reports from the health check links are returning an empty file."
Answer: 254.0

User story: "As a precautionary measure to prevent unexpected EFS disk use,  puppet-duracloud-mill should add a cron job to the sentinel that will delete any content-item.tmp file over three hours old."
Answer: 1829.0
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: The following error is occurring on the client when trying to upload a file with the following content id and local path:   content id : "na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg"      exception:     work/logs/complete.log.1:ERROR  2017/07/25 22:33:34 [pool-3-thread-2]  (SyncWorker.java:68) [run()] - Exception syncing file  /srv/perkins/duracloud/spaces/dpc-archive/content/na_LIC/liclc012/Xanthoparmelia  coloradoënsis/0307290_1.jpg was Content not added due to: dpc-archive  work/logs/complete.log.1:Caused by:  org.duracloud.error.ContentStoreException: Error attempting to add  content 'na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg'  in 'dpc-archive' due to: Response code was 500, expected value was  201. Response body value: Error attempting to add content  'na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg' in  'dpc-archive' due to: exception putting object  na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg into  akiaib3fqeybieeestya.dpc-archive: errorCode=SignatureDoesNotMatch,  statusCode=403, errorMessage=The request signature we calculated does  not match the signature you provided. Check your key and signing  method. (Service: Amazon S3; Status Code: 403; Error Code:  SignatureDoesNotMatch; Request ID: 41A6A511B4EC8AC4)  work/logs/complete.log.1:Caused by:  org.duracloud.error.ContentStoreException: Response code was 500,  expected value was 201. Response body value: Error attempting to add  content 'na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg'  in 'dpc-archive' due to: exception putting object  na_LIC/liclc012/Xanthoparmelia coloradoënsis/0307290_1.jpg into  akiaib3fqeybieeestya.dpc-archive: errorCode=SignatureDoesNotMatch,  statusCode=403, errorMessage=The request signature we calculated does  not match the signature you provided. Check your key and signing  method. (Service: Amazon S3; Status Code: 403; Error Code:  SignatureDoesNotMatch; Request ID: 41A6A511B4EC8AC4)  work/logs/complete.log.1:INFO   2017/07/25 22:33:34 [pool-3-thread-2]  (SyncWorker.java:111) [retryOnFailure()] - Adding  /srv/perkins/duracloud/spaces/dpc-archive/content/na_LIC/liclc012/Xanthoparmelia  coloradoënsis/0307290_1.jpg back to the changed list, another attempt  will be made to sync file.  
Answer: 7348.0
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: "In the current mill configuration we are using instance storage and EBS volumes for temporary disk space.   There are a couple of suboptimal implications of this arrangement:     1.  In the case of the sentinel there is a small possibility of audit log data loss in the sentinel is terminated abruptly since  new log files are pushed to S3 at the end of each log writing session.     2. In order to prevent disks from filling up, every instance must provision enough storage to accommodate the worst case scenario with regard to disk space requirements.  In other words,  since file chunks can be as large as 5GB each node must have at least  threadcount x 5 GB   storage space available in addition to any other overhead ( logs,  programs, os, etc).  Since most instances are using only a fraction of this storage space at any given time, we  are incurring unnecessary storage costs.    Using EFS solves these two problems.   With EFS we don't need to worry about losing data on a disorderly shutdown of the sentinel because EFS data persists across instances.   Regarding the second issue,  you pay for what you use with EFS.   So while EFS is 3x more expensive the EBS per gigabyte,  we expect to use a small fraction of the amount of disk space (probably 1/10th or less) for which  we are currently provisioning.  Another benefit is that we can affordably use many more smaller instances since we don't need to worry about provisioning for adequate disk space.  "
Answer: 291.0

User story: "Due to the increased importance of being able to support the AWS multipart upload features, and the decrease in prominence of OpenStack-based public cloud options, the OpenStack-based storage provider options are to be removed from DuraCloud."
Answer: 394902.0

User story: "The notifications email sender should be configurable so that non-DuraSpace DuraCloud providers will send mill notifications to the proper place."
Answer: 11321.0

User story: "In preparation for sharing puppet-duracloud-mill  with TDL, remove unnecessary dependency on puppet-server which will remain private."
Answer: 40302.0

User story: In order to make manifest downloads more efficient,  add a "compress" parameter.  When present,  the manifest will be returned as a zip archive.
Answer: 30163.0

User story: Downloading the manifest for large spaces can tie up http connections relatively long periods of time.   The longer the period of time, the more likely it is for a client to experience a network failure.  To mitigate this problem,  it would be helpful to be able to generate and retrieve manifests asynchronously.    A simple approach would be to accept a "generate" parameter. When present the response would return a 202 http code and a link to the manifest to be generated in the Location header.
Answer: 30165.0

User story: "It would be useful to be able to deploy the mill on beanstalk rather than relying on the Puppet configuration."
Answer: 2523.0
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: "Some possible approaches:     1.  synctool sends a header with each api call.  2. durastore looks for header of updates and adds synctool version to an existing log message  3. Sumo report shows us versions by account for the last month."
Answer: 1582.0

User story: "Currently the synctool is only checking for the existence of a manifest file and verifying that the original file checksum matches manifest checksum when deciding whether to resync.  In cases where a chunk is missing in DuraCloud,  the synctool will not upload the missing chunk as one would expect.    This issue will be considered resolved when you can delete a chunk from a successfully uploaded chunked file, run the synctool and have it correctly repair the file by transferring only the missing chunk."
Answer: 3445.0

User story: "As a precautionary measure the synctool should check the checksum value coming back from durastore again the value passed to durastore.  Currently we are assuming that durastore is correctly performing that check before sending back a successful response.  We should not assume that to be true. "
Answer: 9220.0

User story: "When transferring chunked content,  the synctool is currently retrying individual chunks on failure.  However the chunk manifest is not being retried as it should be. "
Answer: 9224.0

User story: "Currently the manifest is using the spring-jpa default paging mechanism for streaming the manifest which, under the covers, uses limit and offset keywords at the sql layer.  One implication of this is that the retrieval of each page will always require more time than the previous due to the fact that the database must scan through all previous pages before reaching the page in question.  Thus when dealing with large datasets,  manifest retrieval can take hours.      The fix might involve using a different paging strategy.  Rather than using the offset keyword in the sql, it would be more efficient to sort the set in order of the primary key and use the last primary key in each page to skip to the next page."
Answer: 1512.0

User story: "Currently we do not automatically prevent users for exceeding their storage quotas.  Nor do we have any automated alerts to tell us when a space has gone over.    The solution might, on a daily basis, pull a storage total for each storage provider and compare the sum against the limits set in the account management database.  If the limit has been exceeded,  an email would be set to the the duracloud super admin."
Answer: 417470.0
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: ERROR  2016/09/12 23:49:17 [http-nio-8080-exec-32] (SpaceController.java:117) [populateBitIntegrityResults()] - failed to populate bit integrity results due to error:Error attempting to get bit integrity report properties 'space' due to: For input string: "2285979891"  Caused by: java.lang.NumberFormatException: For input string: "2285979891" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) ~[na:1.8.0_91] at java.lang.Integer.parseInt(Integer.java:583) ~[na:1.8.0_91] at java.lang.Integer.valueOf(Integer.java:766) ~[na:1.8.0_91] at org.duracloud.client.ContentStoreImpl.extractBitIntegrityProperties(ContentStoreImpl.java:1253) ~[storeclient-4.1.4.jar:na at org.duracloud.client.ContentStoreImpl.getBitIntegrityReportProperties(ContentStoreImpl.java:1225) ~[storeclient-4.1.4.jar:na]
Answer: 413504.0

User story: "This test should ensure that a 3 GB file is chunked properly through the DuraStoreChunkSyncEndpoint.   Also, make sure that the test is written in such a way that we can easily add in tests for much larger files should the need arise."
Answer: 26.0

User story: "Currently the producer will start up automatically when it is run for the first time.  This change would enable a user to specify a start time in HH:mm:ss format.  If the start time is not set,  the producer will start immediately.  If the specified start time is before the time of execution,  then the producer will be scheduled to run the following day at that time."
Answer: 107.0

User story: "Resetting a root user's profile should reset all user data caches.   Currently a USERS_CHANGED message is being sent with no accountId.  The result is that instances are not registering the change."
Answer: 4162.0

User story: "It should work just like the duracloud elastic beanstalk."
Answer: 1385.0

User story: "1. Remove obsolete dependencies on database  2. Retrieve space counts from storage stats rather than making a content item count by means of looping through all the content ids.  3. Ensure monitor username and password is encrypted  "
Answer: 1317.0

User story: "We need to perform the same config on 4.x that we did on 3.x "
Answer: 5678.0

User story: "As part of the DuraCloud v4.0.0 release process it was discovered that the SyncTool installer only works on Mac when the installer was created on a Mac. This indicates a need to have a more repeatable build and bundle process to ensure that the build process is consistent across releases."
Answer: 601653.0

User story: "Right now we need to pull the whole manifest to get a manifest checksum value for a particular item.  It would be nice if we could access this information directly.  Perhaps it would be useful to have a durastore api that provides this information as well."
Answer: 968912.0

User story: "Update dependencies for duracloud, spring, hibernate, etc.  Resolve any issues the upgrade creates."
Answer: 1.0

User story: "This will be a subclass of the snapshot provider, to provide the ability to push to Chronopolis, not DPN."
Answer: 69235.0
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: It would be nice if we can offer our users an extra insurance policy against accidental deletes.   Instead of immediately deleting content from the primary store,  a "delete" call should result in content being first moved to a "recycle" bin.  Items will live in the recycle bin for a fixed period of time and then deleted (using a bucket policy probably).    
Answer: 599224.0

User story: "In order to cover the case of content disappearing (due to provider failure) from the source provider we must make sure to delete destination store content only if the content is no longer in the source manifest.  Currently if a dup task comes to dup content from a source to a dest provider, if the item doesn't exist in the primary we delete it in the destination.   However  the looping dup producer adds dup messages for items not in the source that are in the destination in order to synchronize any missed deletes.   Thus a file that disappears from the source unexpectedly will be deleted resulting in data loss.    So to fix this problem: if dup task targets a content item that does not exist in the source provider,  ensure that it is not in the source manifest before deleting from destination."
Answer: 1531.0

User story: "HTTP Status 403 - Invalid CSRF Token 'null' was found on the request parameter '_csrf' or header 'X-CSRF-TOKEN'.    Probably is due to the fact that  CSRF tokens are on by default in the new spring security."
Answer: 2059.0

User story: "Current API endpoints:    # Provides a listing of totals for content in a space over a time range  /storagestats/timeseries ? spaceID & storeID & start & end    # For a single day, provides a list of report details for each space in a store  /storagestats/snapshot-by-day ? storeID & date    Should be changed to:    # Summary of a space, listed by day  /report/space/{spaceID} ? storeID & startDate & endDate    # Summary of a store, listed by day  /report/store ? storeID & startDate & endDate      # Summary of a store (for a single day), listed by space  /report/store/{date} ? storeID    - storeID should be optional, default to primary store    Note: No changes need be made to the functionality, just to the REST endpoints."
Answer: 38877.0

User story: "Currently failures are returning 500 errors."
Answer: 39123.0

User story: "https://wiki.duraspace.org/display/DURACLOUDDEV/Building+DuraCloud+Software+from+Source  "
Answer: 99528.0

User story: "As a first step, it would be very helpful if commits to development version were automatically deployed to a test beanstalk environment.  Additionally it would be good if integration tests were run as part of that process.    NB: Since dependencies such as duracloud-db have *-SNAPSHOT versions while each duracloud instance is in development,  it would be good if duracloud-db commits also trigger a rebuild of duracloud and management-console.  "
Answer: 58923.0
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: "https://<account>.duracloud.org does not redirect to  https://<account>.duracloud.org/duradmin as it does in the current production 3.x line."
Answer: 90707.0

User story: "Remove the following from the dev docs:    1. Duraboss (drop)  2. Durastore (new apis)  3. Durastore (drop init api)  4. Duradmin (drop init api)"
Answer: 119699.0

User story: "Currently -Dduracloud.config.file only supports files.  In order to make it possible for us to use a plain vanilla beanstalk ami it would be better for us to load config from S3.     Loading from S3 would make the instances more secure by now storing credentials on the instances themselves.  "
Answer: 1400.0

User story: "DURACLOUD-988 added dependency convergence and the victims enforcer to the enforcer plugin in the primary DuraCloud baseilne. This task is to add them to the Mill, Management Console and Snapshot (bridge) baselines as well."
Answer: 722409.0

User story: "ACLs are currently cached in the ACLStorageProvider in order to improve performance of space reads.  This works fine when a single instance of ACLStorageProvider can be assumed.  However in beanstalk mode we expect that each node may have a copy of the same ACLStorageProviderCache.  Changes to groups or users that occur in the management console will generate a notification to all of these instances.  However,  changes to the permissions made via Duradmin or the Durastore API must also cause nodes to reload their caches.      One approach to resolve the issue will be to have the ACLStorageProvider generate a notification to the other nodes.    It might be useful to include the source IP address in the notification so that message receivers can opt to ignore messages received from themselves.  "
Answer: 59019.0

User story: "Currently inactive accounts are not ignored.  "
Answer: 3313.0

User story: "It would be beneficial to rerun failed bit integrity runs in order to reduce the time spent managing bit integrity failures.     To achieve this end we must  1. Ensure that if an instance of the producer is currently running, do not run.  2.  modify the bit integrity producer to ignore any space that has run successfully within the last 60 days."
Answer: 4448.0

User story: "The following scenarios appear not to cause a cache update in duracloud:    1. Removing a user from an account  2. Adding a new user to an account  3. Updating a user's rights on an account.    also: double check deleting a user from all accounts works."
Answer: 65981.0
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: "This task is to add two new checks to the DuraCloud dependency chain:  1. Add the dependency convergence option to the maven enforcer (https://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html). This compares versions in the dependency tree to ensure that only a single version of any given artifact is referenced in the build.  2. Add the enforce-victims-rule to the maven enforcer (https://github.com/victims/victims-enforcer). This checks the dependency tree against a list of dependencies known to have security vulnerabilities.    After adding these requirements, there will be changes needed in the codebase to comply with any issues that are uncovered."
Answer: 7706.0

User story: "Currently the looping task producers  will enter an infinite loop if a storage provider is missing.  It should retry a few times.  If it continues to fail it should send and an email and move on."
Answer: 7970.0

User story: "As we move towards an Elastic Beanstalk oriented deployment,  we no longer need to support classic two phase init (ie xml posted to the application)."
Answer: 30286.0

User story: "See https://jira.duraspace.org/browse/DURACLOUD-980 for motivation."
Answer: 1054274.0

User story: "This problem applies to both get spaces and get spaces chunked calls.  It appears that this problem was addresses for get content calls.  So the OpenStackStorageProvider performs a url encode as well as some other encoding magic to get things to work properly.   These issues were identified for  jclouds 1.8.0 (the version we're using) in this jira: https://issues.apache.org/jira/browse/JCLOUDS-217 .  According to the issue details it was resolved in jclouds 2.0.0.   Short term solution is to apply the fix to the OpenStackStorageProvider.  I believe the longer term fix is to upgrade to jclouds 2.0.0.  That later fix will likely be somewhat involved since there were major api changes between 1.x and 2.x.   "
Answer: 1285.0

User story: "When a new space is created in an account which has multiple providers, the mill currently sends an email notification. The next step is for an admin to verify that the space should be duplicated and update the duplication policy accordingly.    Unfortunately, this means that there's a manual step that is required for the system to handle duplication for new spaces. Any content that is added to the primary space needs to be managed after the duplication policy is updated, which is often another manual step. This should all be automated.    To make this happen will require either automated updates to the duplication policies, or a transition in the way duplication policies are used.     One solution would be to change duplication policies to specify a default action (used for all spaces) as well as any exceptions. An account with no dup policy would still perform no duplication, but if an account has a policy, the default action (which would often be to copy from S3 to Glacier) would apply to all spaces unless an exception was listed."
Answer: 929069.0
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: "Before we do a release of 4.0 we'll need to performa a mass conversion of storage reports to the new database-based format."
Answer: 155836.0

User story: "No longer supported."
Answer: 140.0

User story: "For beanstalk version implement storage stats pie chart view of space size and space item count as of x day to match what is currently available in duracloud 3.6.0."
Answer: 8646.0

User story: "As discussed in DPS-123, Jim Tuttle from Duke needs a way to easily retrieve bit integrity reports generated by the DuraCloud Mill. This task is to add a new REST API call to the DuraStore API which will allow for retrieving the latest report file."
Answer: 8503.0

User story: "DURACLOUD-949 and DURACLOUD-951 updated DuraStore to connect to the MC database and pull the information needed to work for all DuraCloud accounts. This work also involved caching the database information and refreshing that cache on change notificatoin. This task is to carry that work forward into a similar capability for DurAdmin."
Answer: 14386.0

User story: "Remove duraboss, reporter, report client, and any dependencies on these modules."
Answer: 380.0

User story: "Currently the storage history of all spaces are stored in xml files found in x-duracloud-admin on the various instances.   We want to extract this data and store it in the mill db space_stats table.      To accomplish this task,  we will need a tool that can convert storage reports for a single account by looping through the list of reports,  extracting the data for each space  and inserting a record in the space_stats table."
Answer: 16076.0

User story: "Duradmin must use new durastore storage stats api rather than pulling, parsing and caching results in memory.      The ContentStore interface will need to be extended.   Duradmin code for parsing and caching storage reports must be removed."
Answer: 16081.0

User story: "In the rest of DuraCloud, GB is defined as a multiple of 1000 (a decimal representation.) The Sync Tool currently uses a multiple of 2 (decimal representation). The Sync Tool should be updated to set the GB value to 1000^3."
Answer: 1416.0

User story: "The UI version of the Sync Tool should have a setting (on the configuration tab) which allows for the size of chunks to be set."
Answer: 1424.0

User story: "This is a follow-on to DURACLOUD-952 to remove the legacy root user which is defined in java opts when the user list is read from the database. This user will still be needed to init in the classic style (until that capability is removed.)"
Answer: 50540.0

User story: "On DuraStore init, an SNS topic subscription is set up. The SNS connection details are stored in the MC DB. When a message comes through that subscription, it picks up what changes were made and updates local cache."
Answer: 85691.0
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: "Currently the synctool's backup thread is running on the same schedule as the directory polling period which is 10 seconds by default.  The back up thread period should not be tied to the polling period.  Instead it should run at least every 5 minutes by default.  Also thread synchronization on on the ChangedList.persist method is causing threads to wait until the backup file is completely written rather than waiting only until the file list is copied in memory."
Answer: 3.0

User story: "DuraStore through beanstalk will no longer have access to a single root user. Instead it will need to allow any user with the root role to have root-level access. This work is to ensure that root user access works properly.    Since DuracloudUser has a root boolean property, we need to take that into account when loading user details managers from the global account repo. Currently we are relying on ROLE_ROOT associations in the account rights."
Answer: 62318.0

User story: "All calls through DuraStore in a beanstalk setup will need to pull account information then perform the expected requests on the appropriate account."
Answer: 62332.0

User story: "All calls going through DuraStore will need to determine the account for which the call should be processed. By default this should be done using the subdomain of the host used for the call. There should also be an optional query parameter added to each API call which allows specifying the accountID, as this will be necessary for testing and may be needed by other scenarios.    Part of this work will be to ensure that the combination of the account and user credentials still ensures that only users with access to an account are able to make calls that affect that account."
Answer: 62354.0

User story: "In order to have all of the information that is needed, DuraStore in beanstalk will need to have a direct connection to the MC database. Much of the code for setting up this connection should be already available from the MC or Mill (share/reuse where possible).    Options for getting the database connection information:  - As system properties specified in JAVA_OPTS (using beanstalk environment variables, note that there is a 256 character limit)  - Use JAVA_OPTS to point to a config file S3 URL, and pull that in on startup.    In order for the DuraStore calls to complete quickly, and to keep the database load down, information from the DB should be cached. This could be done preemptively or lazily, but in either case, there will need to be handling for invalidation, to ensure updates to the database are picked up."
Answer: 62342.0

User story: "Cloudwatch now provides metrics for S3, providing a daily total of files and total size per bucket in an account. We need to use this rather than running DuraBoss for reporting, at least on S3 and Glacier stores. Ideally we can discontinue the use of DuraBoss completely."
Answer: 198801.0
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: From Bill's initial ticket with SDSC:     I'm working with one of our DuraCloud sub-accounts in SDSC Cloud storage,  and am seeing a difference in the number of content items reported by the  container and the number of items in the list when listing the items in the  container.    Specifically, this is in the "colum" account, in the cbmr.admin container.  If I ask for the number of content items in the container, I get back the  number 145956. If, however, I list the items in the container, the  resulting list shows 145814 items.    This seems to have something to do with some oddly named content items in  the container (this is DuraCloud customer content, so I can't say why they  used these names.) An example of this type of file:    DOCS/LMosesLLM_personal/Pictures/06272012_MOFONE/foursquare/cache/http%3A%2F%  2Fplayfoursquare.s3.amazonaws.com%2Fuserpix_thumbs%2FZ2QM4EHBZ423VKYX.jpg    The file named above is one I expect to be in the container. When I  retrieve the list of items in the container, this item isn't in that list,  though there is a series of other files which have a very similar path. If  I request this file directly (by first escaping all of the percent  symbols), I am able to get the file back, so it does exist in storage, it  just doesn't show up when the contents of the space are listed.    If you could shed some light on what might be going on here, that would be  quite helpful.  *****  Below is the link to the SDSC issue.  https://footprints.sdsc.edu/MRcgi/MRlogin.pl?DL=31724DA1
Answer: 1320579.0

User story: "According to this announcement: https://aws.amazon.com/blogs/aws/aws-storage-update-new-lower-cost-s3-storage-option-glacier-price-reduction/?sc_ichannel=em&sc_icountry=global&sc_icampaigntype=launch&sc_icampaign=em_148542750&sc_idetail=em_2049897831&ref_=pe_430550_148542750_7, Amazon is now offering the option of a lower cost S3 tier for infrequently accessed data. This task is to transition all DuraCloud content to this new option.    The best way to take advantage of S3 - IA is via bucket lifecycle policies. Because of the additional cost of content deletes in the first 30 days, it would be best to set these policies to transition content from S3 Standard storage to S3 - IA storage after the content has been stored for 30 days. This policy should be created when a new space is created (via the S3StorageProvider)    As part of this work, the current S3 task which transitions content to Reduced Redundancy storage should be replaced with a task that adds the bucket policy for S3 - IA to an existing bucket. To complete this transition, a script will need to be written which uses this task to update all current accounts.    The storage class init parameter should also be removed (from both app-config, and from the MC). It no longer makes sense to support reduced redundancy storage."
Answer: 16113.0
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: In order to stream mp3 files through Cloudfront, the files themselves must have the ".mp3" file extension, but the streaming URL must be requested without the file extension. Currently, there is a check to make sure that a call to get a streaming URL corresponds to a content ID already in storage. In this case, though, the content ID and the "stream" ID don't quite match.    This task is to remove the check to see if a content ID is in place before a streaming URL can be requested. This should solve the problem noted above, and make it possible to pre-generate URLs for content files prior to upload, which may be useful as well.
Answer: 159.0

User story: "Users with USER role should be able to see the bit integrity notice and should be able to see and use the space manifest button. Currently these are only available to users with ADMIN role or above."
Answer: 99661.0

User story: "Storage reports are currently being generated on DuraCloud instances. Now that the Mill is in place, it would make more sense for these reports to be generated there. As part of this transition, consider the potential of using the manifest database to generate these reports more efficiently."
Answer: 393360.0

User story: "Each of the DuraCloud apps currently responds to a /init REST call with either a 200 if the app is initialized and ready for use or a 503 if the app is available but not yet initialized.    This task is to update this to change the 503 to another code. The reason is that Apache also returns 503 responses as a DuraCloud instance is starting when it is not yet able to make a connection to Tomcat. This results in the Management Console thinking that an instance is ready to be initialized when  it is not yet available.    Note that this change will require a companion change in the MC to ensure that the correct HTTP code is expected on init."
Answer: 120870.0

User story: "Discussions with Ilya Kreymer from webrecorder.io have suggested that there could be an integration with that service to allow playback of WARC files directly from DuraCloud storage, which could be quite beneficial for Archive-It users storing content in DuraCloud.    In order to make this happen, the DuraStore API needs to support range requests, allowing for only portions of a file to be retrieved from storage, rather than the entire file. This is supported in S3 and OpenStack Swift, so should be something we can support across all providers."
Answer: 1495137.0

User story: "This chunk is not right.    <storageProviderAccounts>    <storageAcct ownerId='0' isPrimary='true'>...</storageAcct>    <storageAudit>...</storageAudit>    <millDbConfig>...</millDbConfig>  </storageProviderAccounts>    millDbConfig and storageAudit should be siblings of storageProviderAccounts.    See xml document for correct format."
Answer: 11778.0
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: "It has been noted several times that the sync deletes feature in the SyncTool can be dangerous. It provides the opportunity for a user to delete their entire corpus of content if it's not used carefully.    This task is to add a warning dialog when anyone selects the option to turn on the sync deletes feature which describes the dangers and asks them if they are sure this is what they would like to do."
Answer: 43293.0

User story: <authentication-provider user-service-ref="userDetailsSvc"/> 
Answer: 4642.0

User story: "If one gets through 99 percent of a chunked file before failing, on restart all chunks will be retransferred."
Answer: 1666010.0

User story: "The rest api should support a call to get the last bit integrity report for a space.  It should include, along with the body of the latest report, the status of the report (success if all went well, failure if there are errors) as well as the date the report was completed.  The properties should be accessible through a HEAD call, while the content (as well as properties) will be accessed with a GET.   "
Answer: 7.0

User story: "This feature allows initial transfers of data sets to proceed without the usual checks to see if the content is already in DuraCloud (since we know that it is not.) Instead, all files will simply be transferred.  The need for this feature comes from GSU. With a large set of small files (4.7 million under 1 MB), the overhead of doing the checks for each file was slowing down the overall transfer considerably. "
Answer: 2710.0

User story: "Neither parse nor format operations are threadsafe."
Answer: 20.0
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: This feature was requested by one of our users:   Michael Bolton michael.bolton at tamu.edu:  We are using DuraSync to move files into DuraCloud and that is working very well for us.  I noticed the Sync process seems to capture more metadata than the web upload interface; however, I do want to add additional metadata to our files.  I am using the REST API and found the curl examples to be very helpful.  I used a command along the lines of the following, essentially straight from the examples.  curl -X POST -H "x-dura-meta-color: green" https://duracloud.tdl.org/...  While it added the color attribute it seems the other x-dura-meta headers were deleted or dropped.   Prior to adding the new attribute, the properties were  HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=90BAD6077906B4A41F72FF36E8F1996E; Path=/durastore; Secure x-dura-meta-content-file-modified: 2014-07-11T08:37:53.053 x-dura-meta-creator: mbolton Content-MD5: c9135109016547f9f794e8fdcd82826f x-dura-meta-content-file-path: C:\TDLDuraCloud\TDL_DuraCloud_Msgs.pdf x-dura-meta-content-file-created: 2014-07-11T08:37:50.050 x-dura-meta-content-file-last-accessed: 2014-07-11T08:37:53.053 Last-Modified: 2014-07-18T19:01:06 ETag: c9135109016547f9f794e8fdcd82826f Content-Type: application/pdf Content-Length: 1066710 Date: Thu, 25 Sep 2014 17:39:54 GMT  After the update command  HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Set-Cookie: JSESSIONID=8B9A61C48BD38752EACE88FEB07D2C58; Path=/durastore; Secure Content-MD5: c9135109016547f9f794e8fdcd82826f x-dura-meta-color: green Last-Modified: 2014-09-25T17:40:11 ETag: c9135109016547f9f794e8fdcd82826f Content-Type: application/pdf Content-Length: 1066710 Date: Thu, 25 Sep 2014 17:40:15 GMT   The only x-dura-meta header in the list if the color attribute.  I confirmed this via the web interface and the properties are gone.  I would have thought adding an attribute would not affect existing properties but maybe I assume too much.  Do I need to read existing properties and then add them back in with my updates?  Thanks 
Answer: 1847474.0

User story: "Michele was having trouble launching the installer 3.1.1 on Mavericks.  At first it seemed that the problem was the lack of java.  Danny had her install java 8.  Still no luck.  Danny was able to reproduce: Symptoms:   After downloading the latest synctool installer (3.1.1), double clicking on the icon appears to do nothing.  The system log is showing this output less than completely helpful output:  Sep 29 15:54:30 panna com.apple.launchd.peruser.501[241] (com.bitrock.appinstaller.81696[42342]): Job failed to exec(3) for weird reason: 13 Sep 29 15:54:30 panna Finder[259]: 8837325: Attempting to SIGCONT to pid #42342 failed, with errno=#3, or the process failed to actually start Sep 29 15:54:30 --- last message repeated 2 times --- "
Answer: 1274.0

User story: "Add maven plugin: http://maven.apache.org/plugins/maven-checkstyle-plugin/ which will fail the build if code style fall outside of the expected parameters."
Answer: 1840415.0
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: "Namely, make sure that storeID parameter can be null and if so, the primary storage provider is used."
Answer: 3.0

User story: "- DuraCloud would add a new user attribute which defines an IP address or range (using CIDR notation) - Once this attribute for a user is filled out, all future attempts to log in as that user (both in DuraCloud instances and the Management Console) would require that the user be coming from that IP address or range. - Users would be able to update this attribute in the Management Console. - Note: This feature would need to support multiple IP address/range entries, as there could be 2 or 3 specific IPs where the user needs to be able to log in from."
Answer: 305355.0

User story: "- DuraCloud would continue to use CloudFront to stream files, but would add an option to limit access to streamed content. There would be two options when setting a space to be streamed: open streaming (which is how we do streaming now) and restricted streaming.(the new feature). - When using restricted streaming, no files would be directly accessible. Instead, to expose a file, a new DuraCloud REST method would be provided which could be called to retrieve a signed URL that could then be used to stream the file. - The new REST call would require providing the username and password of a DuraCloud user with administrative rights. - The new REST call would require an ending date and time parameter, after which the returned URL is no longer valid. - The new REST call would allow for providing an optional parameter indicating the IP address or range of addresses that can be used to access the content.  The consumer of this service (UNC in this case) will be responsible for: - Verifying that a user of their system should have access to the content that is to be streamed - Making the call to DuraCloud (with appropriate DuraCloud permissions) to request and retrieve the signed URL - Inserting the URL into an RTMP player (e.g. Flowplayer, JWPlayer, etc) which will allow the user to view the content"
Answer: 291990.0

User story: "Currently, to determine the ideal number of threads to maximize throughput, users of the SyncTool need to run the SyncRate tool with a variety of settings, record the speed values, then compare them. This is time consuming and difficult. This task is to make determining the thread number for optimal throughput as simple as possible."
Answer: 10590.0

User story: "DURACLOUD-869 added a prefix option to the SyncTool. This task is to provide a way for users of the UI to make use of that new feature."
Answer: 28520.0

User story: "The UI for the SyncTool should provide an option to set the number of threads used for processing. This can just be a drop-down box on the configuration screen.  "
Answer: 50504.0