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: "Release 3.0.0 introduced logs that are written out by DuraStore on all read and write actions that occur. This task is to add lumberjack to the instances hosting DuraStore, update the logstash configs to capture the information in ElasticSearch properly and create a Kibana dashboard to display it."
Answer: 69300.0

User story: "In DuraCloud 2.x, there was a call on the DuraBoss REST API which allowed for retrieving a manifest of content in a space (a listing of content items with their checksums). This was removed in 3.0.0, since it was based on the old auditing system. This task is to implement a new REST method which supports retrieving a manifest from the content index."
Answer: 562660.0

User story: "In a discussion with NCDCR, they noted that they would like to be able to break up their data set, and perform syncs at lower levels in their path hierarchy, but are prevented from doing so because they would like the full directory path to be included in the content ID. Currently, the only way to do this is (in a Windows environment) to either run the Sync/Upload tool from a high level directory, or move content around. Moving content around, in their production storage system is not practical.  The new feature requested to resolve this problem: Allow for a prefix option, that would be prepended on all content items being transferred.  To keep this simple, the prefix provided would apply to all files in all specified content directories."
Answer: 27075.0

User story: "Currently the log statements in storage providers (I looked mostly at the S3StorageProvider) that indicate how users are making use of the system (addContent, getContent, etc) are at the DEBUG level, meaning that they aren't included in the logs of production instances.   In order to understand how users are actually making use of the system, it would be very helpful to tie these usage metrics into the log tracking system (LogStash, ElasticSearch, Kibana). A necessary step in this process is to have these log statements moved to the INFO level, so that they are actually produced by the running code in a production environment."
Answer: 378638.0

User story: "Several customers have requested the need for a tool that will allow them to perform a bulk delete of a subset of content in a space. They need a tool that will allow them to, first, specify which content to delete from a space and then, second, perform a bulk delete for that content."
Answer: 7671.0

User story: "In DuraCloud release 2.4 an issue with the JClouds library that was used (the latest at the time) was that it would not perform reauthentication when the auth token expired. This required a work around in DuraStore. The issue has now been fixed: https://issues.apache.org/jira/browse/JCLOUDS-178.  This task is to update to the latest JClouds library when possible."
Answer: 492426.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 a cloud service strategy meeting on Aug 6, 2013 (https://wiki.duraspace.org/display/DSPINT/2013-08-06+-+Cloud+Service+Strategy) there was a discussion about a need expressed by UNC to have a way to view images in DuraCloud as a gallery, in order to aid in the finding of images in their collection.  I was thinking that this could be accomplished with an html/css/javascript app that is stored in one of the user's spaces, and allows them to select a space (if that's actually necessary, could be hard coded to the one that is their image library) and view a set of images. The javascript would need to make calls to the DuraCloud REST API to get the list of content items and display each one. The images would likely be scaled down a bit, to make browsing easier, and clicking on them would display the (slightly) larger size. The REST API would also be used to allow paging through the content items (and not trying to display too many at once). The option to specify a prefix for filtering would need to be there, and the user would need to be able to see the full content ID of the item they are viewing, since that will be the link back to the full size archival image on their internal system.  There is an expectation that the UNC folks will be generating the necessary low-res images that would be viewed through this gallery viewer, and would load those images into a DuraCloud space."
Answer: 939988.0

User story: "It would be handy to be able to optionally list a space contents as it  will appear when retrieved.  That is, only list contentIds as they will appear after they are restitched (do not show chunks or manifests).  It's a kind of dry run for the retrieval tool in a way."
Answer: 1320.0

User story: "It would be nice to be able to optionally list all the md5s as well as the raw list of contentIds for a space."
Answer: 1092193.0

User story: "The current DuraCloud AMI is based on Ubuntu 11.10, which reached end of life in May of 2013 (according to https://wiki.ubuntu.com/Releases). The version to move to should be determined when this issue is worked, but it likely makes the most sense to stick with an LTS version."
Answer: 520188.0

User story: "DURACLOUD-759 added a hidden password for the Sync Tool. This task is to make use of the same environment variable to pick up the password for the Retrieval Tool. This will help to keep the functionality of the two tools in sync."
Answer: 30091.0

User story: "In DURACLOUD-774 (in particular, the changes in code r1072) changed over the Sync Tool from using log4j to using logback as the underlying logger. This task is to update the Retrieval Tool in the same way."
Answer: 725943.0

User story: "This task is to provide a way, on Windows, Mac, and Linux systems for a Sync Tool that is running on shutdown to restart and continue running after a system restart."
Answer: 49387.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: "There have been a variety of customer questions and issues reported in using the Sync Tool which mostly boil down to the user's system not having the necessary Java version or not having Java installed at all. This task is to provide actionable feedback to users as they attempt to use the Sync Tool, which will allow them to more easily resolve the problems and get the Sync Tool operational."
Answer: 14521.0

User story: "This task is to update DuraBoss to connect to the relational database used to store what has traditionally been the dataset used by the Management Console. The end goal of this integration is to allow DuraBoss to be initialized with only an account ID. All the rest of the necessary initialization information should be retrieved from the database."
Answer: 2548498.0

User story: "This task is to update DurAdmin to connect to the relational database used to store what has traditionally been the dataset used by the Management Console. The end goal of this integration is to allow DurAdmin to be initialized with only an account ID. All the rest of the necessary initialization information should be retrieved from the database."
Answer: 2548492.0

User story: "This task is to update DuraStore to connect to the relational database used to store what has traditionally been the dataset used by the Management Console. The end goal of this integration is to allow DuraStore to be initialized with only an account ID. All the rest of the necessary initialization information should be retrieved from the database."
Answer: 2548495.0

User story: "This task is to implement the initial version of the DuraCloud 3.0 service architecture, as discussed here: https://wiki.duraspace.org/display/DSPINT/DuraCloud+3.0+Service+Strategy. The goal of this architecture is to replace the existing (DuraCloud 2.x) service infrastructure with a system that can more efficiently and more reliably manage actions over large content sets."
Answer: 2548498.0

User story: "This work is to clean out the legacy DuraCloud service implementation code from the baseline once it has been replaced by the DuraCloud 3.0 service architecture."
Answer: 469539.0

User story: "Now that there is a solid UI as part of the Sync Tool, and because of the seemingly constant issues with java applet technology, the multi-file upload applet should be removed from DurAdmin and the single file upload option should be re-instated.  This work should occur alongside DURACLOUD-775, which provides easy access to the Sync Tool."
Answer: 38565.0

User story: "The current OpenStack storage provider implementation uses both the client originally provided by Rackspace (which has now been discontinued) as well as the JClouds library (which is now the client recommended by Rackspace for Java development: http://docs.rackspace.com/sdks/guide/content/java.html).  This task is to update the OpenStack and Rackspace storage providers to use only JClouds."
Answer: 172453.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 improvement is dependent on the Shibboleth branch. When a user logs out, he/she should be redirected to a page that specifies that complete logout requires closing the browser (ala the MC)."
Answer: 2634905.0

User story: "This improvement is dependent on the Shibboleth branch.  A DuraCloud-branded 403 page should be rendered when an authenticated user who is not authorized to access DuraCloud tries to log in."
Answer: 2634907.0

User story: "The SyncToolUI should be updated to provide better feedback to users when they have selected a space to sync to which they do not have permissions to write to. Since there is not a simple way to collect this information up front, this task is to pay attention to exceptions that are coming back from a sync activity to determine if it is likely that they are a result of lacking permissions, then provide information to the user that will allow them to be aware of he problem and a suggested resolution."
Answer: 241925.0

User story: "DuraCloud has a dependency in the POM to ActiveMQ 5.2, an old version.  The version does not formally support Java 7, supported in DuraCloud 2.3.  In particular, specialized settings are needed to work with Java security.  DuraCloud 2.3 has been tested using ActiveMQ 5.7 and 5.8 so the update should require little effort and have little impact."
Answer: 2675285.0

User story: "After requests from several trial and customer users, the synchronization tool should provide a configuration option/flag in which the entire directory path is included upon upload. Currently, the top level directory is ignored and not persisted in the naming of the content items that are uploaded via the sync tool. This new flag for the sync tool would enable the entire folder structure to be included in the name of the uploaded content."
Answer: 285219.0

User story: "When content is stored in Glacier, attempts to download, view, copy, or edit the properties of that content will result in an error (http status 409). This task is to provide users with useful feedback when they attempt any of these actions on a content item in Glacier.   More specifically, when a call is made on a Glacier content item via the storeclient, a ContentStateException is thrown. (If the content item was recently added or has been retrieved from Glacier, it will simply download as expected) This task is to show the user an appropriate error message indicating that the content is in Glacier. For now, that error message can indicate that the user should contact DuraCloud support if they wish to retrieve that content item."
Answer: 20483.0

User story: "DURACLOUD-737 allows the Sync Tool to preserve local time stamp information in DuraCloud content item properties. This task is to add an option to the Retrieval Tool which will set the time stamps of files that have been retrieved (assuming that those files have time stamp information recorded in DuraCloud)."
Answer: 20140.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 update DurAdmin to provide very obvious links which allow users to download the client-side tools (Sync Tool, Upload Tool, UpSync, Retreival Tool)."
Answer: 263644.0

User story: "This task is to copy the UpSync tool from the DfR codebase into the DuraCloud codebase in order to expose it as a DuraCloud feature and in order for ongoing development to occur.   Once transferred, the tool should be tested with DuraCloud by both technical and non-technical staff to ensure that it can be easily installed, it functions properly, and that there are no usability issues."
Answer: 29575.0

User story: "The Glacier storage provider allows for very low cost storage, but retrieval costs can add up very quickly. This task is to limit the ability of users to request content retrievals in such a way as to minimize the risk of high costs."
Answer: 2712887.0

User story: Three users within the past month have had the misunderstanding that selecting the checkbox next to a space name would then allow them to view their content. Each time I had to field either a support email or call and explain that they should *not* select the checkbox next to the space name to view the content, add content, edit content, etc. but that they should only click on the name to select/highlight the space to view the content.  Ideally either clicking directly on the checkbox or the space name will select the space (add the checkmark) and both actions will behave identically: they will display the content of the space with all the other associated actions. The two actions that we lose by doing this are the "delete selected space" and "edit properties" on the space level. I believe we should determine another way for those options to appear.
Answer: 12154.0

User story: "This task is to introduce the use of durable subscriptions in place of standard topic subscriptions in order to have a better assurance that messages are not lost in the event of an interruption of a JMS connection. The failover directive, which is currently in use, allows connections to be re-established, but there is the potential for messages which were sent during the time when the connection was down to be missed.  More information can be found here: http://activemq.apache.org/how-do-durable-queues-and-topics-work.html http://activemq.apache.org/manage-durable-subscribers.html"
Answer: 2864304.0

User story: "This task is to provide an option for the Sync Tool which will allow users to supply their DuraCloud password in a way other than via the command line options. The reason this is an issue, is because the full command used to run the sync tool remains available in the process list of the machine on which the sync tool is running.  The suggested fix for this concern is to allow users to define an environment variable which contains their DuraCloud password, which would be picked up by the Sync Tool if the -p option is not provided. "
Answer: 351543.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 DurAdmin, each space name has to its left a checkbox. Users expect that selecting the check box will perform the same action as selecting the space name text. Instead, selecting the checkbox (of one space or more) brings up a multi-select display.  A user from UCAR/NCAR was recently caught by this issue, and could not understand why the listing of content items was not showing up until they contacted Carissa for assistance.  This task is to discover and implement an alternative to the current UI functionality described above which will be more easily understandable.  From Carissa: Three users within the past month have had the misunderstanding that selecting the checkbox next to a space name would then allow them to view their content. Each time I had to field either a support email or call and explain that they should *not* select the checkbox next to the space name to view the content, add content, edit content, etc. but that they should only click on the name to select/highlight the space to view the content.   Ideally either clicking directly on the checkbox or the space name will select the space (add the checkmark) and both actions will behave identically: they will display the content of the space with all the other associated actions. The two actions that we lose by doing this are the "delete selected space" and "edit properties" on the space level. I believe we should determine another way for those options to appear.
Answer: 39295.0

User story: "As the synchronization of content between storage providers becomes automated (DURACLOUD-642), it becomes unnecessary for users to edit content in their secondary provider. In order to maintain an assurance that content remains consistent between providers, the ability for users to make changes at their secondary storage provider should be removed. They would still be able to view and download all content, but no add/update/delete operations would be allowed.  This task is to update the DurAdmin UI to ensure that users with role user/admin/owner do not have write access to secondary stores."
Answer: 56171.0

User story: "This feature is to expose AWS Glacier as an option for content storage. http://aws.amazon.com/glacier/"
Answer: 233274.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 an option to the Sync Tool which ensures that it does not overwrite any existing DuraCloud content. This means that when a file on the local file system, which has previously been added to DuraCloud, changes, it is not simply uploaded again.  There are a few choices that need to be made for this new feature to be added: 1. When a file already in DuraCloud changes on the file system, is the updated file transferred to DuraCloud or not. If so, the original file will likely need to be renamed to prevent collision. 2. How is the list of updated files communicated to the user. Are they printed to the console (stdout), or written to a file? Is this consistent between interactive mode and run-to-completion mode? 3. How does this feature impact the upload tool?  A comment from the State of North Carolina about how they envision this feature:  "Our ideal upload tool would allow us to specify a local directory to update in the cloud, and the tool would then identify and upload new files (new files defined by file name and path), and alert us to any files that have changed (same file name and path but new checksum hash) and not upload the files that have changed (or upload them in a way that doesn't overwrite the files in the cloud). We would want to make sure that the process of uploading content is kept totally separate from any risk of editing existing content in storage."
Answer: 494111.0

User story: When any event occurs in DuraStore (space/content is added/updated/deleted) a message is sent. This task is to update that mechanism to skip sending those messages for the "administrative" spaces in DuraCloud (x-duracloud-admin, x-service-out, x-service-work).   There is currently no need for updates on administrative files, and dealing with all of the messages generated by admin file updates wastes effort.
Answer: 2961921.0

User story: The Sync Tool currently logs a variety of "errors" when it is running normally. Many of these log statements have to do with calls to determine if a file currently exists in DuraCloud. The attached file includes errors showing up in the log (provided by users at UTK.)  This task is to clean up the logging outputs so that only actual errors are logged as such.
Answer: 3670190.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 create a utility which can loop through a set of directories and capture the timestamp information (Creation Date, Modified Date, Access Date) on each of the included files. That timestamp info should be written to a file (so that it can be archived locally) as well as written as metadata to each files's corresponding DuraCloud content item. (The expectation here being that the Sync Tool has already done the work of moving each file to DuraCloud.)  The capability to capture time stamp information was added to the NIO package in Java 7 (http://docs.oracle.com/javase/7/docs/api/java/nio/file/attribute/BasicFileAttributes.html), thus this utility will need to be built and run using Java 7.  This task is in direct response to needs expressed by the State of North Carolina archives and libraries. Everyone in their offices uses Windows (either 7 or XP), so this utility needs to be tested on Windows."
Answer: 119828.0

User story: "This task is to transition DuraCloud to be built and run using Java 7. There are a few reasons for this transition:  1. Oracle has announced that Java 6 will hit end-of-life in Nov 2012 (http://www.oracle.com/technetwork/java/eol-135779.html) 2. Java 7 has been available for over a year, and is becoming more prevalent 3. Java 7 has new capabilities. One specific need is the capability (in NIO) to read/write file creation, modification, and access timestamps 4. We need to support customer use of Java 7 with our client-side tools (e.g. sync tool)"
Answer: 116526.0

User story: "Based on feedback from the State of North Carolina, they would like the sync tool to preserve the local timestamp information for individual files (both the creation and modified dates/times). They would like this information passed into DuraCloud via the sync tool, available for viewing within DurAdmin, and then retrieved/restored properly by the retrieval tool when content is downloaded."
Answer: 180858.0

User story: "This task is to allow for passing a list of files to the Sync Tool which should be ignored when performing a sync. The simple case is for the file to include one full path to a file per line. Any file in this list would not be pushed to DuraCloud. Directories in the list would be excluded as well, along with all files and subdirectories in each directory.  A more complex implementation would allow for using wildcards to indicate files that should not be included. The capabilities of rsync should be reviewed in order to determine the most convenient syntax for the exclusions."
Answer: 225128.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 Sync Tool currently generates three logs: complete.log, duracloud.log, and synctool.log. It was noted by the SaaS4 customer that these logs together took up an unnecessarily large amount of hard drive space. They noted that over 10 days, after pushing 500 Gb of data, the logs totaled around 300 Gb. This is clearly too much space consumed by logs.  This task is to limit the log outputs. This could include removing the complete.log, as well as ensuring that logs are cycled properly, so as to not consume more than a set amount of space."
Answer: 3005339.0

User story: "As noted in testing described here https://wiki.duraspace.org/x/8YzvAQ, the work of transferring very large numbers of files from one storage provider to another is not particularly well suited to hadoop. This task it to create an alternative content duplication method.  The requirements are as follows: - Must be able to move content from any provider to any other provider - Must be able to be deployed onto multiple server instances in order to share the load and speed up processing  It may be necessary for this to be a multi-step process. Perhaps something like: 1. Run a process with the source space and the number of instances that will be used for the job as parameters, and it splits up the work into an input file for each worker node. 2. Each worker node is spun up and initialized with the proper information to do the work, including their portion of the job, as defined in step 1. 3. After all nodes have completed step 2, a final process verifies the transfer by comparing the source and destination spaces.  The goals of this work: 1. Provide a method which can reliably transfer large numbers of content files from one provider to another. 2. Provide a starting point for the further work of developing a large file processing capability within DuraCloud that does not rely on Amazon EMR."
Answer: 3022420.0

User story: This task is to update the log management settings for the Tomcat server on DuraCloud AMIs. These settings are contained in /etc/logrotate.d/tomcat6.  Log rotation settings should be updated to rotate on size (perhaps 256M) rather than date, and limit the number of rotations which are kept (to perhaps 3).  A full list of options for these settings can be found with "man logrotate".
Answer: 4531.0

User story: "This improvement is to leverage /mnt on EC2 instances for temp files, at the least. /var/log/tomcat6 should link to /mnt  An analysis should also be performed to determine if /home or the webapps should use /mnt as well."
Answer: 85350.0

User story: "Update the sync tool to be better able to handle periods of time where the instance has become unavailable. This is particularly important to allow the SyncTool to continue to run normally across DuraCloud instance upgrades.   A likely strategy is: When a transfer fails, check to see if the instance is available before doing a retry, if its not, then wait for ~5 min and try again. When the instance becomes available again, resume file transfers."
Answer: 141308.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 image preview section of the UI displays an icon (with mountains) when either the Image Server is not on, or when the space is not publicly viewable. This tends to prompt lots of user questions around why they cannot view an preview. This is especially an issue for multi-tenant accounts, where the user is not able to start the Image Server or make their space publicly viewable. This task is to remove the image preview area of the content item display."
Answer: 408.0

User story: "When an admin is logged in and looking at the space detail, the pie charts will display below the fold.  In order to see them, the user scrolls down.   However when the user clicks on a line chart data point, the pie graphs will be updated, but the user will not notice because they are not visible.   It would be much better if the history line chart would scroll to the top of its container when the line chart is clicked."
Answer: 3097485.0

User story: "This task is to allow for using a Sword client to push content into DuraCloud"
Answer: 3099001.0

User story: "Now that the Executor is in the business of running services on behalf of users, we should ensure that users aren't able to interfere with those activities. This update will allow us to indicate which services should be read-only for all users (other than root). There will need to be a visual cue to indicate to administrators that they are able to see services, but are not able to change (update, deploy, undeploy) them."
Answer: 11609.0

User story: "This improvement is to make sure that the ManifestGenerator for Bagit manifests delimits the checksum from the path with two spaces instead of the current single space character."
Answer: 22648.0

User story: This improvement is to add labels to the two y-axes of the "History" "Byte and File Counts Over Time" storage graphs. Currently it is not exactly clear that the left-hand y-axis represents cumulative file size, and that the right-hand y-axis represents cumulative file counts.
Answer: 244822.0

User story: "This task is to make the Administration tab on DurAdmin available only to root users."
Answer: 30189.0

User story: "As more and more important information for the management of DuraCloud is pushed into the x-duracloud-admin and x-service-out spaces, it becomes increasingly important that the files in those spaces not be removed or changed. This task is to provide only read permissions to those spaces to administrators. Root users will continue to have full access.  As a note, the logo item in x-duracloud-admin will need to be managed in a different way once this change is in place."
Answer: 3123295.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 a preservation perspective, it is often a concern that files stored in DuraCloud can be accidentally overwritten. This is especially an issue when tools (such as the sync tool) are used to monitor local files for changes an copy them to DuraCloud, since a file that is accidentally changed would then overwrite the good file in the backup DuraCloud system.  This task is to implement a change in DuraCloud such that existing files could be preserved as-is when new files are added. This capability should be optional, allowing the user to determine if they would prefer files to be overwritten or "versioned".  Versioning features from cloud storage providers, particularly S3, should be consulted to determine if they could be used directly, or simply as reference for the DuraCloud implementation
Answer: 2748510.0

User story: The "Size" property for spaces (the number of bytes stored in that space) is always available for spaces in Rackspace, because this information is provided, but is never available for spaces in Amazon and some other providers. This task is to remove the "Size" property from the space display when it is empty.
Answer: 251357.0

User story: "This feature is to integrate the ability to request backups and restores to/from Chronopolis into Duradmin. "
Answer: 3124159.0

User story: "This feature is to leverage the Chronopolis REST client to integrate the business tier of requesting: - backups to Chronopolis - restores from Chronpolis - notifications on errors and completions - polling of in-process requests"
Answer: 3124162.0

User story: "This feature is to create a java client for the Chronopolis REST Server. https://github.com/<USER>chron-notifier  Further details of the usage of the Chronopolis client can be found here: https://wiki.duraspace.org/display/CHRONO/DuraCloud+Chronopolis+Integration "
Answer: 274602.0

User story: This task is to determine the feasibility of using SDSC as a DuraCloud primary store. Beyond function feasibility, the performance differences of an EC2 to SDSC configuration should be compared to the standard EC2 to S3 configuration.  As a side note, it would be interesting to explore SDSC's openness to supporting "salted" server-side checksums.
Answer: 3124395.0

User story: "Once the new set of service plans have been nailed down, this task is to make any updates that are necessary to make new plans available and remove unneeded plans."
Answer: 40256.0

User story: "Add "
Answer: 261921.0

User story: "See attached error:  There appears to a problem calling remotely into duraservice via duradmin."
Answer: 3127607.0

User story: "Probable solution will involve caching the primary content store on the client."
Answer: 3129108.0

User story: "This improvement is to create the SystemUserCredential in a similar was to how RootUserCredential is created, via a default username/password over-written by system properties. Once this is done, DuradminExecutorImpl.java should be evaluated for exchanging root-user with system-user."
Answer: 3137847.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 create a java client (similar to storeclient, serviceclient, and executorclient) to simplify interactions with the Auditor REST API."
Answer: 3139194.0

User story: "This task is to complete the Bit Integrity Handler in the Executor. Design notes can be found here: https://wiki.duraspace.org/display/DSPINT/DuraBoss+Design"
Answer: 11.0

User story: "This task is to implement the Media Streaming Handler in the Executor. Design notes can be found here: https://wiki.duraspace.org/display/DSPINT/DuraBoss+Design"
Answer: 6.0

User story: "This improvement is to refactor the Executor, ManifestGenerator, and Auditor interfaces to a common project that can be shared between DuraBoss and the various DuraBoss clients. Additionally, these interfaces should be implemented by the utilities themselves as well as the clients."
Answer: 2.0

User story: "This task is to create a Java client for calling the manifest REST methods in DuraBoss."
Answer: 46.0

User story: "This task is to create a java client (similar to storeclient, serviceclient, and reportclient) to simplify interactions with the Executor REST API."
Answer: 13106.0

User story: "It would be nice to have way to generate a snippet for streaming audio/video  that can be embedded directly into any page. "
Answer: 3169589.0

User story: The purpose of this feature is to guide the user to the content manifest for the space as well as enable them to peek at the recent activity.  The "peek" might be equivalent to head -10 audit-log.
Answer: 3180578.0

User story: "This improvement is to include the authenticated user-id of the user performing content actions over the durastore API. At the least, the user-id needs to be included on the ingest event message.  This is in support of the DfR: Object Creation Service."
Answer: 23465.0

User story: "Since services will no longer be run directly by users, there is no longer a need for the Media Streamer service to produce the contents of the Viewer space. Those generated files are not used as part of the service, they are only provided as examples for how a user might integrate the media streamer service with their own website.  This task is to: - Add a copy of the generated files (updated to be more generic) with some surrounding instructions to the DuraCloud documentation - Update the Media Streamer service to no longer generate these example files"
Answer: 19174.0

User story: "Release 2.0 added the ability for users to select a button on a space and turn on media streaming for that space. This task is to ensure that the streaming URL provided by the Media Streamer service is added to the metadata of the space when it is being streamed, so that the user has access to it."
Answer: 3219842.0

User story: Please add "forgot password" and "create profile" links underneath the log-in button of DurAdmin exactly like they appear on the Management Console.
Answer: 3533809.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 improvement is to refactor the RackspaceStorageProvider to OpenStackStorageProvider. Since we currently have three storage-providers that all expose an OpenStack API, the RackspaceStorageProvider (which is coded to the OpenStack API) should now be abstracted up as the base class of the three implementations: Rackspace, SDSC, and HP. Each of these inheriting classes should have their own names displayed in error and logging messages."
Answer: 5840.0

User story: "Services are being automated and users are no longer required to run the bit integrity service themselves, but they still need to know that their content is being verified. This task is to include on the UI, likely in the space details area, an indication of when the most recent successful bit integrity check was run over the content in that space.  In the event that the most recent bit integrity check resulted in an error, we (DuraCloud staff) will need the opportunity to investigate the issue and correct it if possible before the issue is displayed to the user (this may also be done in an automated fashion.) If it turns out that the error requires user intervention, then it would be nice to be able to have that be indicated in some way on the UI, calling out specifically which files need to be addressed."
Answer: 78598.0

User story: "This improvement is to update the Duplicate on Change service to allow configuration at the space-level. Namely, the service should be able to run on a subset of the total spaces of an account. It would be ideal if this improvement also allowed the spaces over which Dup-on-Change is configured to copy from the primary to any of the secondary providers."
Answer: 243182.0

User story: "This improvement is to increase the probability that the space creation method will work on secondary providers. Currently, the S3StorageProvider has a wait cycle in the createSpace() method that retries adding the space-metadata file until the bucket has been created and registered. A similar wait cycle should be added to the createSpace() method (or rather appropriate 'setSpaceProperties' method) of: - RackspaceStorageProvider - AzureStorageProvider"
Answer: 15808.0

User story: "When trying to select a set of spaces to work on, I often select several spaces and then accidentally deselect them all accidentally by clicking a few pixels off of another checkbox.   The solution here is to add padding to the checkbox element so that it is not necessary to be so precise with the mouse position."
Answer: 2910.0

User story: "This task is to make it possible for Duradmin to integrate with existing Shibboleth-based authentication and authorization systems. This is needed in order to satisfy the requirements of Internet2 and DfR.  See discussions related to this issue here: https://wiki.duraspace.org/display/DFR/Shibboleth+Thread"
Answer: 3238150.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 create an HP Storage Provider. HP is still in its testing phase, so this will allow us to test the new provider more easily, and determine the extent to which it meets the expectations of the DuraCloud application.  HP uses OpenStack, so the code required for this implementation should be minimal."
Answer: 7.0

User story: "Image thumbnails are generated on the fly and then cached by the djatoka image server. The latency in thumbnail generation can sometimes leave the user wondering what happened to the image.   Providing a visual cue to show that something is happening, albeit slowly, would improve the experience."
Answer: 11643.0

User story: "When viewing an image in a public space with the image server service running, make the thumbnail larger and center the layout."
Answer: 11659.0

User story: "This task is to break out the information in the storage reports and display it instead on the main Spaces tab. The space-specific charts should be included on the Space Detail page. The provider-specific charts should be displayed in the detail area that is currently shown as blank when selecting the Spaces tab. The top-level all-providers charts will no longer be displayed. Both the provider-specific and space-specific charts should still provide the option to view historical charts and data."
Answer: 121011.0

User story: "This task is to limit the Administration tab in DurAdmin to be viewable only by root users."
Answer: 403179.0

User story: Update the following items in DurAdmin:   - Change "Space ID" and "Content ID" to "Space Name" and "Content Name" respectively - In the footer of every DurAdmin instance page, ensure that DuraCloud has the "c" capitalized. - In the footer of every DurAdmin instance page, the link to DuraCloud.org should come before DuraSpace.org - In the footer of every DurAdmin instance page, replace the current "Help Desk" link with a "Help Center" link which points to: https://wiki.duraspace.org/display/DURACLOUD/DuraCloud+Help+Center - The title of every DurAdmin instance page (that appears in the browser tab) should be DuraCloud: Login, DuraCloud: Spaces, etc. or something similar (not "DurAdmin :: DurAdmin: Login" or "DurAdmin: Spaces") - Change "DuraCloud Administrator" to just "DuraCloud" - Make the Dashboard tab available only to root users
Answer: 120912.0

User story: Update the following items in DurAdmin:  - Remove the option to "add one item", change the "add many items" link to simply be "add items" - Update the image on the copy button to appear consistent with the other buttons (currently appears to be lower quality) - In the Content Detail panel, make content size number understandable (at least include a unit - "bytes") - In the Content Detail panel, set all buttons to be the same color (light gray perhaps)
Answer: 18820.0

User story: "Same as https://jira.duraspace.org/browse/DURACLOUD-512 but for non-hadoop services that operate on lists of items."
Answer: 3054.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 test the DuraCloud client tools (primarily Sync Tool and Retrieval Tool) and make updates that are necessary to allow the tools to continue to run even if the DuraCloud instance becomes unavailable for a short period of time. The period of time to be tested against should be the time that is required to upgrade a DuraCloud instance to a new version. This will allow DuraCloud users to keep their tools running even across an upgrade cycle.  A likely strategy is: When a transfer fails, check to see if the instance is available before doing a retry, if its not, then wait for ~5 min and try again. When the instance becomes available again, resume file transfers. "
Answer: 3267345.0

User story: "This task is to update the sync tool such that it creates and updates a textual transfer log including all files which are added or updated in DuraCloud along with their checksum. This file would only include files which were successfully transferred to DuraCloud.   Ideally the format of this file would follow the format expected by the bit integrity service, so that after doing a fresh transfer of a full dataset into DuraCloud this transfer log could be compared to the space via the bit integrity checker service."
Answer: 3269855.0

User story: "Remove the dependencies on space access by having duradmin use the acls instead.  It is also necessary to make it clear to the user how to enable public access on a space if no public acl has been set. Additionally the public group should be highlighted in the UI to amplify its uniqueness. "
Answer: 7.0

User story: "This improvement is to add messaging over the durastore calls to StorageProvider.setSpaceACLs(). The configuration for this is in: durastore/src/main/webapp/WEB-INF/config/aop-config.xml A new advisor (ala SpaceUpdateAdvice) will needed to be created as well."
Answer: 169178.0

User story: "Currently, the cache for space properties is loaded the first time a user attempts to access a storage provider. If this user is a non-admin user, and there are many spaces in the account, this action can take several minutes. This task is to transition to loading the cache when the instance is first initialized, rather than waiting for a user to access the instance, greatly lowering the likelihood that any user will have to wait while the cache is populated."
Answer: 73549.0

User story: This task is to sort the listing of items in the Permissions section of the content item display in DurAdmin.  Groups should be displayed above users, and both sets should be sorted alphabetically (A-Z). The "public" group, when added, should always be displayed at the top of the list.
Answer: 60377.0

User story: "This improvement is to deprecate the setSpaceAccess and getSpaceAccess methods on the StorageProvider and ContentStore interfaces."
Answer: 52.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 improvement is to refactor the implementation of space access from the 'space-access' property to an ACL property (acl-group-public). In addition to cleaning up specialized logic for space access, handling space access as an ACL will allow a single call to the underlying storage providers to be made in determining access rights in Spring Security instead of a call for space access and a separate call for space ACLs. "
Answer: 36983.0

User story: This update is to not display the "Services" tab nor the reports tabs under "Dashboard" if the user who is logged into duradmin only has ROLE_USER. Rather, only users with ROLE_ADMIN should be able to see the services and reports tabs.
Answer: 10818.0

User story: "This feature is to enable multi-map header values throughout the application for content and space properties. The capability should be enabled for the entire stack: storageproviders, to REST, to StoreClient, to Duradmin."
Answer: 11235.0

User story: "This feature is to add a new StorageProvider wrapper implementation to facilitate filtering the spaces listed in a getSpaces() request. The primary objectives are to: - provide a way to only return spaces that are either 'open' or are accessible to the calling user - improve performance so that each request for the space listing does not require querying the properties of each space from the underlying storage provider.  Below are some implementation suggestions:  1. in StorageProviderFactoryImpl.getStorageProvider()         * wrap storageProvider with a new ACLStorageProvider()  2. ACLStorageProvider         * overwrite: getSpaces()         * cache spaces and space acl properties "
Answer: 24871.0

User story: "This update is to modify app-config, SecurityUserBean, and security-users.xsd, as appropriate to support the inclusion of ACL 'groups' during instance initialization."
Answer: 4430.0

User story: DurAdmin should be able to graphically display folder and file hierarchies in a similar fashion that is available on a local machine. Currently, the naming convention to indicate hierarchical files (ex. folder1/folder2/folder3/filename.txt) is not sufficient from a user perspective. It is expected that the interface will allow them to create "sub-folders" or spaces within spaces, etc. that will map to the local directories that the content was stored in.
Answer: 92635.0

User story: "Please add a refresh button to the space listing as well as to the content listing within a space. Currently a space is not reloaded after content items are added, and a user must either (a) reload their entire browser window or (b) click on the space tab and renavigate to the appropriate space to see the newly added content items."
Answer: 39312.0

User story: "This feature should update the durastore spring security definitions to limit access as defined in: https://wiki.duraspace.org/display/DSPINT/Space+Level+ACLs+-+design"
Answer: 19436.0