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: "This feature should add the new method to the StoreClient: setSpaceACL() This method should take a spaceId and a map of 'usernames' and/or 'groupnames' and their associated privilege (read or write), and set the ACL for the given space. "
Answer: 13265.0

User story: This feature is to create a UI in duradmin for managing space-level ACLs. It will likely be a button in the righthand pane, similar to the "edit" button for space metadata. The functionality should enable Admins to add/remove 'users' and/or 'groups' to the space ACL with permissions of 'read' or 'write' (which implies read). A potentially attractive UI widget would be the one that renders two, side-by-side boxes containing usernames, and arrows allowing the moving of usernames from one box to the other. 
Answer: 38908.0

User story: "The creation of the Upload Tool included several back-end changes to the Sync Tool. This task is to make improvements to the front-end of the Sync Tool to: - Display the progress of file transfers when printing status - Allow for individual files to be watched as well as directories"
Answer: 3382303.0

User story: "This feature is to establish a means of deploying the UploadTool via Duradmin as a signed-applet, webstart app, or other."
Answer: 4438.0

User story: "When the image server or media streamer services deploy, it would be nice to have some UI notification indicating which files are not supported. For example, image files that are CMYK or have other property files that would prevent them from being available in the viewer. This would also be similar for media files that have unsupported file extensions or codecs. Exactly how this would be presented on the UI is unclear. It could be indicated in the service detail area  (9 of 10 files compatible and ready for viewing/streaming) or it could be indicated at the content item level (after clicking on a content item having some notification in the content details panel)."
Answer: 3401033.0

User story: "This task is to add support in DuraStore for long-running actions that can be run over content. Some examples of these kinds of tasks are: multi-file delete, multi-file copy (within and between providers), and multi-file property add/update/delete. It may make sense to implement this feature using the existing tasks infrastructure."
Answer: 134079.0

User story: "This feature is to provide an integration with Archive-It so that users with Archive-It content may seamlessly push their collection into DuraCloud."
Answer: 809352.0

User story: "This task is to make it possible for users to rename DuraCloud spaces. In order to do this, space names will need to no longer be directly tied to the bucket/container names of the underlying storage provider. One way to do this is for the name of a space to become a property of that space. A side benefit of this is that we should be able to remove many of the naming limitations we currently have on space names."
Answer: 3401109.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 is to create and maintain a manifest (space-id, content-id, md5) of all content held in the primary storage provider. A listener should update the manifest whenever content is added or deleted from Durastore. The format of the manifest should be compatible with the expected input format of the bit-integrity service."
Answer: 247368.0

User story: This feature is to expose the copy-content-across-storage-providers functionality within Duradmin. This needs to include the option to "multi-select" content items to be copied as well as only selecting a single item.  Likely this will be an addition to the existing content copy UI element. The interface should optionally allow the user to indicate the destination storage-provider.
Answer: 133711.0

User story: "This feature is to provide the ability to start a DuraCloud instance with a set list of services that will be run on a set schedule. The first example of such an auto-run/scheduled service is Bit-Integrity."
Answer: 261870.0

User story: "This feature is to provide space-level ACLs. Specific users and groups should be able to be granted read/write access to a given space."
Answer: 42016.0

User story: "This feature is to integrate the SDSC Cloud as another underlying StorageProvider."
Answer: 9004.0

User story: "This improvement is to set the log level of messages in the MediaStreamService to INFO or DEBUG from the current WARN. "
Answer: 3418557.0

User story: "This improvement is to investigate and potentially implement an update to the StorageProvider.addContent() interface method or an addition of a parallel addContent() method that optionally takes object-properties along with the content-stream.  As an example, the current ContentRest.addContent() method performs two calls to the StorageProvider: addContent() & setContentProperties(). The number of calls made to the underlying storage-provider could be cut in half if these two calls were combined.  The AmazonS3Client interface, the Rackspace FilesClient, and the Azure IBlobContainer all support calls for including metadata along with the call for adding content."
Answer: 76459.0

User story: "This task is to make command line options as uniform as possible among the current set of command line utilities: sync tool, retrieval tool, chunker, stitcher. There are currently several inconsistencies that need to be cleaned up:  - Use -c for content directory (as used by sync and retrieval tools). Currently stitcher uses -d and chunker uses a compound -a option - The chunker should support -i (store-id) - The chunker should use -s (space-id) rather than including it as part of -a - The chunker should use -h (host) and -r (port) rather than -c"
Answer: 3432934.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 by default only expose the user content in the UI storage reports. The administrative content to be filter is currently found in the following spaces: - x-duracloud-admin - x-service-out - x-service-work  The implementation may be done at the time of report statistics collection or in the UI, toggling admin spaces on/off. "
Answer: 3428669.0

User story: "This improvement is to extract out the failed items from the output report of unsuccessful service runs in order to make the errors more clear for the user. The implementation will likely require updates in the reporting UI as well as in the underlying service infrastructure. "
Answer: 167103.0

User story: "This improvement is to have different informational messages (and underlying service properties) for when a service fails versus when the results of a service run contain failures. Examples of service failures are unrecoverable exceptions, OOM, failed hadoop startup, etc. Examples of result failures are bit integrity discrepancies, unsuccessful image conversions, unsuccessful duplications, etc."
Answer: 160133.0

User story: "This task is to add messaging support to the new copyContent() method added to the StorageProvider interface. A new topic should be added to carry messages related to copy operations. Once the messages are being sent, the two services which are listeners, Duplicate on Change and Media Streamer, need to be updated to listen for copy operations and react appropriately."
Answer: 34.0

User story: "This improvement is to add a new REST method to each of the four existing webapps: - durastore - duraservice - durareport - duradmin  That authenticates against anonymous users and returns a response code of: - 200 = is initialized - 503 = is not initialized"
Answer: 10291.0

User story: This task is to add a link or links to the DurAdmin dashboard which allow a user to easily download the DuraCloud utilities (sync tool, retrieval tool, etc). It would also be useful to have links pointing to the documentation for each of the utilities that can be downloaded.  Update the existing "Help" link to open a new window with this page: https://wiki.duraspace.org/display/DURACLOUD/DuraCloud+Help+Center Add a tab on the Dashboard beside the Storage and Service report tabs called "Tools" with the content listed here: https://wiki.duraspace.org/display/DSPINT/DurAdmin+Tools+tab
Answer: 11648.0

User story: This task is to add a new service plan: "all", that includes all services.
Answer: 3467.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 item is to ensure that an error is thrown back to the user when a space to be created has a name which exceeds the maximum name limit. Currently the name is just truncated, and the truncated name isn't displayed until a refresh of the UI.  See S3ProviderUtil line 133 for the spot where the S3StorageProvider likely does the truncation. All current active storage providers (S3, Rackspace, Azure) should be checked for this same behavior.  Example of a space name that is too long (for S3): duracloud-1-1-0-snapshot-service-repo-trial-test "
Answer: 8903.0

User story: "EasyMock has rolled the class extension project under the base project and deprecated EasyMock ClassExtension. This task is to update the top level pom to use EasyMock 3.0+ and refactor all tests which use org.easymock.classextension.EasyMock to use org.easymock.EasyMock instead."
Answer: 272046.0

User story: "This feature is to provide users a way to copy a single item from one storage provider to another storage provider (or within the same storage provider). The implementation will likely be similar to the ContentStore.copyContent(), but will contain an optional source storeId. This effort should also include exposing the cross-provider copy functionality at the ContentRest level of Durastore. "
Answer: 81575.0

User story: "This feature is to add an additional method to the storeclient, namely, moveContent(). This method will simply call copyContent() followed by deleteContent()."
Answer: 4802.0

User story: "This task is to include a version number in the printed output of the sync and retrieval tools so that it's easy to determine which version is being used."
Answer: 14343.0

User story: "This task is to update DurAdmin to serve its pages as strict XHTML. The mime type used should be: application/xhtml+xml. The DOCTYPE header should also be specified as <!DOCTYPE html> which is the recommendation for HTML5."
Answer: 3468662.0

User story: "This task is to add an option to the Retrieval Tool which will pull down the list of items in a given space (or list of spaces), rather than actually retrieving them. This list will be written to a file.  There is an existing tool in duracloud-utils named the space-lister-tool which already provides this capability, so it may be useful to borrow code from that implementation.  This should result in a single new command line option (--list-only perhaps) that, when included causes the space list to be stored in the content directory rather than files."
Answer: 977918.0

User story: "This feature is to expose the StorageProvider.copyContent() method through the DuraStore REST API as well as update the storeclient. However, this feature should not be implemented until the patch submitted to Rackspace has been incorporated into the Rackspace java-client baseline. https://github.com/rackspace/java-cloudfiles/pull/18"
Answer: 22888.0

User story: "This feature is to add UI support for single content copy/rename operations."
Answer: 56744.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 update is to re-add the DuraCloud favicon to the duradmin application. In release 1.0.0, its rendering was somehow dropped."
Answer: 15006.0

User story: "This feature is to add a new CloudSync service. The service will likely be a webapp service (ala j2kservice). Note: CloudSync itself should probably by updated to take its working directory as an initialization argument."
Answer: 67786.0

User story: "This improvement is to restyle the Dashboard Storage and Services tabs to have a consistent styling with the rest of the duradmin application."
Answer: 68830.0

User story: The name of the service which was selected needs to be displayed on the screen used to configure the service. Currently there is just text that reads "Configure the Service", which isn't very helpful.
Answer: 69026.0

User story: Currently, when deleting a space of reasonable size there is a dialog that spins for a while, then the space is removed from the spaces list. But if the list of spaces is refreshed, the "deleted" space shows up again. In the background a process is still running to delete the space, but there is no way for the user to know that this is happening.  This task is to make it clear to users when a space is in the process of being deleted.  
Answer: 94049.0

User story: "This improvement is to ensure that a monitor thread is in place when a service is reconfigured.  A service can be reconfigured while it is either still running, or after it has completed. Since a reconfigured service retains the same deployment-id, a service that is still running will continue to be monitored by the original monitoring thread. However, a service that is complete needs to have a new monitor thread started since the service is effectively restarted via a reconfiguration."
Answer: 3278.0

User story: This improvement is to add a link to the services "Report" property to display (possibly as a flyout?) a tabular form of the service results.
Answer: 259692.0

User story: "The purpose of this task is to swap out the current XStream implementation of the DuraReport storage report generation to use JAXB. The main reason for this is to be able to provide an XML schema for the data that is being generated, so that the information can be more easily retrieved and used."
Answer: 11727.0

User story: "This improvement is to provide the StorageProvider interface support to: 1. copy an object stored within DuraStore to another space within the same storage provider 2. rename an object stored within DuraStore to a new content-id within its existing space  All three storage providers (Amazon, Rackspace, Azure) provider REST-API support for 'copy', but it appears that only the Amazon and Azure java clients expose this functionality.  http://docs.rackspacecloud.com/files/api/v1/cf-devguide-20110629.pdf http://docs.amazonwebservices.com/AmazonS3/latest/API/ http://msdn.microsoft.com/en-us/library/dd894037.aspx "
Answer: 66398.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 additional storage report that is a cumulative on-going report which is updated each time a new storage report completes. The information in this report will be an entry for each completed storage report that provides the top level report information. Mime type information would be left out, and other information in the detailed report may be excluded as well. The goal of this report is to be able to create graphs that show the change in content stored over time.  This report could work like the completed services report in that it could be cycled to start a new file monthly.  Information should be included in the cumulative report  that allows for the creation of links to the detailed reports as well as cross-links to the detailed report charts. This could just be the detailed report content ID."
Answer: 3549481.0

User story: "This task is to create a schema and serializer for the list of content-ids returned from ServiceReport.getCompletedServicesReportList(). The expected xml should look something like this: <service-report-ids>     <service-report-id>Service-Report-2011-06-27.xml</service-report-id> <service-report-ids>"
Answer: 21974.0

User story: "This improvement is for the following two classes to implement the same interface: org.duracloud.client.ServicesManager.java org.duracloud.duraservice.mgmt.ServiceManager.java"
Answer: 2782.0

User story: "This improvement is to add a new service property across all services that have a completion (success or failure) that notes the content-id of the service result file. This property should be set upon service completion."
Answer: 18538.0

User story: "This improvement is to decouple the dependency on the content-id of the service.xml file of a service registry from the space-id of the registry itself. Currently, the content-id is required to be identical to the space-id with the addition of the '.xml' extension. The service.xml content-id should be allowed to be any name."
Answer: 126495.0

User story: When a service is deployed via duradmin, an entry is created detailing the: - service - hostname - status  The 'status' is apparently populated when the service is deployed and never updated as the actual service status changes through the course of processing. This improvement is to keep the status info in the UI entry up-to-date by pulling the content from the "Service Status" property instead of from the Deployment.status The current/accurate status info is also displayed on the right hand side, under the service details.
Answer: 104568.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 client-side tool which provides a nice user interface for managing bulk upload tasks.  This tool should provide a UI that allows files to be uploaded via the following methods: - file/directory selection dialog  A progress bar should be provided which indicates the status of the upload, specifying which file is being uploaded and the progress of the transfer.  It may make sense to use the SyncTool in the background to manage file transfers."
Answer: 217414.0

User story: "This feature is to add a new storage adapter to connect to iRODS/Chronopolis, ala S3, Rackspace, & Azure. The base code has already been provided by <USER>"
Answer: 129.0

User story: This improvement is to reflect the completion state of bulk services as "success" or "failure". Currently, the service state remains "started".  Affected services: bit integrity checker bulk image transformer bulk duplicate on demand  Additionally, the end-time of the service should be captured in the service properties.
Answer: 20341.0

User story: This improvement is to reflect the completion state of non-bulk services as "success" or "failure". Currently, the service state remains "started".  Affected services: bit integrity checker bit integrity checker tools image transformer  Additionally, the end-time of the service should be captured in the service properties.
Answer: 11678.0

User story: This feature is to omit the rendering of service properties that have names prefixed with "System ". These are service properties that are useful for monitoring and scripting, but are probably confusing for end-users of Duradmin.
Answer: 38899.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: I notice the DuraCloud terminology for name/value pairs attached to Content are "metadata".  But I'm suggesting thats probably a poor term to describe those properties attached to the content, especially in the face of presenting such a tool to a larger IR/Library community.  Renaming these to be Properties or Attributes would lessen possible confusion on the intention here.  1.) Metadata can be multi valued repeatable (subject=this, subject=that) while Content properties in Duracloud are a Map of non-repeatable name/value pairs.  2.)  I am seeing a great need to clearly separate in our DSpace Abstract Storage API what are properties and what are metadata, as Datastructures for Properties are valuable for the api, but not applicable in the metadata case.  We will more than likely begin to separate these two cases in our Data Model when mapping to "Fedora", "DuraCloud" and "JCR".  There is an outstanding question as to how to best manage "multivalued properties" for instance JCR does support multivalue properties in its API (http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/class-use/Property.html) and Fedora supports returning multivalued DC elements in its output and the storage seems loose enough that multi valued properties may exist, but that setting them may have unexpected results. https://wiki.duraspace.org/download/attachments/4718716/foxml_reference_example.xml?version=1&modificationDate=1217847185364  Clarification on the differences of DuraCloud Properties, Fedora Attributes/Properties and other systems, with any intended alignment intentions would be very helpful to the community at large.  For instance, based on current work to port content from DSpace, Fedora, other CMS and repositories, can a set of best-practices emerge for what should/should not be placed into such properties?
Answer: 106716.0

User story: "In order to make the issues of eventual consistency an issue that does not concern the users of DuraCloud, DuraStore should be updated to provide a cache for the content which is stored. This could mean either storing the file locally first, then making the call to push it to the provider, or wrapping the stream in order to write the file locally while it is being stored at the provider. These local files would be used to fulfill GET requests that come in shortly after the file has been stored. The files in the cache would be removed once there is a greater degree of certainty that the file will be available on all following requests to the provider (perhaps just after a certain time period has elapsed.)  Note that one benefit to storing the files locally prior to pushing them to the provider would be that we could know the file size and generate the checksum locally before making the provider request, meaning that we could ensure that the file reached DuraStore correctly before passing it along to the next location. This may also become useful for handling large files that we intend to pass to the provider using a multi-part upload."
Answer: 3611408.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 no text is displayed."
Answer: 211826.0

User story: "The notification for delete space has no close function (button) so the user can continue.  It the operation is longer that the session-time out the browser remains on the cached pop-up until the user refreshes the browser, generally resulting in request to log in again.  The pop-up would be improved if the user could close it and do more work.  The system should lock the space being deleted from subsequent operations.  The UI space page should show a status on the page (on the space being deleted) and the should be updated when the operation is complete if the session is still active (otherwise the space is simple no longer listed)."
Answer: 3614474.0

User story: "This task is to update the S3StorageProvider to make use of Amazon's multi-part upload option for S3 when content is large enough to require chunking. This would mean that rather than storing our chunked file parts (and associated manifest) in S3, we would use the multi-part tools to push up the pieces and assemble them again in S3.  Since the MD5 for the entire chunked file is not available from S3, we will need to calculate it on transfer and store it as metadata."
Answer: 3618679.0

User story: "This feature is to have the services.xml service-repo manifest generated for each of the various DuraCloud account package types: - archiving / preservation - media access - professional - trial"
Answer: 51717.0

User story: "This improvement is to have the services.xml service-repo manifest created during the mvn 'package' phase instead of during 'test'."
Answer: 50593.0

User story: "Currently, when re-initializing duraservice, due to caching, some elements do not take on the new re-initialize values. This improvement is to determine and implement what is required to make duraservice re-initialization work as if it were being initialized from scratch."
Answer: 186125.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 0.9 release the first binary installation package was created. This allows system admins to deploy an instance of DuraCloud without needing to build from source. This was a good first step, but there are a few pieces which could make the process smoother:  - Include wars with names that do not include version. When the jars are dropped into tomcat with the release version included in the file name, they are not deployed to the expected context path (i.e. rather than a context path of /durastore it is instead /durastore-<version>. The installation package zip file includes the version number, this should be sufficient. - Include the app-config jar, as this is needed to configure the instance. - Include an example properties file to be used with app-config.jar for instance initialization. - Include a default/example logback.xml file which can be used within the service bundle home. - Update included run.bat file to properly pick up environment variables in a Windows environment - Allow for the use of a local service repository (handled by DURACLOUD-402) - Update the included readme.txt file to have complete instructions for standing up a DuraCloud instance using the files provided with the installation package. Parts of this document can refer to the wiki for further explanation, but ideally, the entire process would be well enough defined in the readme such that the links to the wiki would be optional reading."
Answer: 122506.0

User story: "It is currently required that the service repository for a DuraCloud instance be hosted on another DuraCloud instance. This task is to allow the service repository to be hosted within the same instance. This will both simplify the deployment of stand-alone DuraCloud instances (for users of the open source platform) and lead the way toward allowing multiple service repositories to be associated with a single instance."
Answer: 138604.0

User story: Most of the REST API methods that return XML today use text/xml, but application/xml is a actually a better choice due to character encoding issues:  According to the specification of the text/* media types (RFC2046), if a charset parameter is not specified in the declaration of mime type (at the end of the Content-Type value, ala "text/xml; charset=utf-8", it must be assumed that the body is encoded in US-ASCII.  The "encoding" declared in the XML declaration is supposed to be ignored.  Here are a couple online posts that further explain the problem:  *  http://annevankesteren.nl/2005/03/text-xml *  http://www.grauw.nl/blog/entry/489  It's clearly the intent that DuraCloud REST API methods that return XML are encoded in UTF-8 (because the xml declaration says so), but according to the standards, because text/xml is used instead of application/xml, and the Content-Type is not declared with a "charset=utf-8" MIME parameter, the xml declaration is supposed to be ignored by clients and they should assume US-ASCII.
Answer: 13693.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 provide the option for users to select a list of spaces when configuring the Duplicate on Change service, then only perform duplications for items in those spaces. One reason for this feature is to allow users to choose to not duplicate x-service-out and x-service-work spaces."
Answer: 698140.0

User story: "This improvement is to add method security over UserDetailsService.getUsers() to limit access to this call to ROLE_ADMIN."
Answer: 3681666.0

User story: "This update is needed to support creating a service-config.xml document that is named the same as the allowable service registry name. The old convention was: duracloud-0.9.0-service-repo The new convention is: duracloud-0-9-0-service-repo "
Answer: 23024.0

User story: This task is to remove the user-management capabilities ("Adminstration" tab) from Duradmin, since this functionality is being moved up the the account-management-app.
Answer: 27693.0

User story: "This task is to create a UI dashboard for displaying and downloading reports on storage.  REST API calls should be available from which the storage report information can be gathered. A UI will need to be created to be able to display the information in the reports.  The reports will likely be in XML, so XSLT is an option for display."
Answer: 200583.0

User story: "Provide a way to generate a report containing: - details from running services  The details should include at least the following information:  - tbd  The reports should also be available for retrieval through a REST-api"
Answer: 172392.0

User story: "This improvement is to remove from the service output space the interim manifests that the bulk-bit-integrity service creates once the final report has been created. These manifests are: bit-integrity-metadata-results.csv bit-integrity-results.csv"
Answer: 105069.0

User story: "This feature is to expose a utility for sending emails. It should consist of both a general interface project and a corresponding implementation project."
Answer: 13191.0

User story: "This improvement is to change the bulk bit integrity service to run its MD5 metadata collection post-processor in hadoop instead of with a single process on the main duracloud instance. This enables the service to run within hours instead of days for spaces exceeding 50,000 items."
Answer: 3.0

User story: "This improvement is to extend the durastore API to support bulk operations such as updating metadata for multiple content items, retrieving metadata for multiple items/spaces, etc."
Answer: 1190665.0

User story: "Service reports that appear in the service-output space need to have an additional differentiator so that services that are run multiple times in one day do not overwrite one another."
Answer: 21483.0

User story: "This new feature is to provide an extension to the REST APIs to support retrieval of usage report information. The report data would be the same that is exposed on the dashboard."
Answer: 198168.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 media streaming service via CloudFront does not include access controls for individual content items and further, has persistent URL addresses for content that can be determined."
Answer: 243324.0

User story: "request to allow admin users to set permissions per user on the space basis"
Answer: 339613.0

User story: "This task is to set up a listener for new files which are added to spaces on which streaming is already enabled, and enable those files for streaming as well."
Answer: 301309.0

User story: "This improvement should allow the user to selectively sync specific files based on subdirectories, prefixes, and/or suffixes using the synctool."
Answer: 3739507.0

User story: "This task is to allow the user to select multiple spaces for the media streaming service to stream."
Answer: 303751.0

User story: "This improvement is to ensure that spaces that contain up to 1 million items can successfully perform a bit-integrity manifest verification."
Answer: 6677.0

User story: "This improvement is to allow services built within a particular version of the baseline (say 1.4.0) to specify compatibility with dependency DuraCloud-osgi bundles from another version (say 1.3.0)."
Answer: 24.0

User story: This improvement is to more accurately display the service status state of bulk services. Currently, bulk image conversion and bulk bit integrity checking are processed in two steps: 1. hadoop processing 2. post processing on duracloud instance  The service status shows conflicting messages. The "Job State" is "COMPLETE" when the hadoop step is done, but the "service status" shows "Post Job Processing" for bit integrity, and nothing for image conversion.  More accurate and consistent status messages need to be put in place across the services.
Answer: 155700.0

User story: This improvement is to change from the current pattern of storing user credentials in-memory as plain text to, storing the hash of the credentials in-memory and having authN perform the same hashing (SHA256?). See Spring Security for adding a "password-encoder" to authentication providers in both 2.x and 3.x versions.
Answer: 62207.0

User story: "This improvement is to ensure that all report-like outputs from services are created in the x-service-out space. Also, the outputs should have a consistent naming convention: <service-identifier>/<report-name> where <service-identfier> = all lowercase with '-' between words if necessary"
Answer: 51911.0

User story: "Currently the output for the Bulk Image Transformer is in a modified CSV format, similar to: name1=value1, name2=value2, name3=value3, ...  This task is to update the output to be in standard CSV format: value1, value2, value3  The first line in the file should a header which indicates the names of the values to follow: name1, name2, name3  The Bulk Bit Integrity service produces this format by allowing the hadoop reducer to produce all of the value lines, then using a post processor to insert the name line at the top."
Answer: 52016.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: When configuring the Duplication on Demand service, if you leave the destination space name blank, the service should automatically create the destination space with the source space's name.  Carissa ran the service leaving the destination space blank (assuming this would occur) and the service ran to completion... service status read: "complete" but no duplicated content was to be found.
Answer: 31952.0

User story: "This improvement is to extend the list of hadoop server sizes that can be chosen in the 'advanced' configuration of bulk services. http://aws.amazon.com/ec2/instance-types/"
Answer: 57990.0

User story: "It would be nice to reverse the order of the upload history in the upload window, so that more recent and/or in-progress uploads appear at the top instead of the bottom of the popup window. Sort of what the Firefox download window does. Putting the recent ones at the bottom requires the user to scroll down to see the progress bars of the recent uploads."
Answer: 20084.0

User story: "The bulk bit integrity service should contain the following updates: - add optional config option that takes a user-specified input listing that is used to verify MD5s after the hadoop servers have generated a new listing.  -- if no listing is provided, the service should compare against MD5s stored in storageprovider metadata  -- this post processing should be implemented as a PostJobWorker"
Answer: 2940.0

User story: "Provide a way to limit access to media being streamed via the Media Streaming Service so that institutions can allow access only to those who have come through their interface and paid a fee to view the content. This may be possible with time-limited or single-access credentials, depending on the capabilities of CloudFront.  This need was raised by Geneva Henry (Rice) during a DuraCloud pilot partner meeting on Dec 13, 2010."
Answer: 2339194.0

User story: "Provide a way to generate a report with at least the following information:   - Number of files for each space - Total size of files stored in each space - Average file size for each space - File types (mimetypes) represented in each space  - Total number of files (all spaces) - Total size of all files (all spaces) - Average size of file (all spaces) - File types (mimetypes) represented (all spaces)  - All of the above information for each storage provider in use  These reports should be available for download and should be stored within DuraCloud so that they can be referenced periodically. At some point we may want to provide a way to schedule the running of such reports (monthly).  This would seem to be a good fit for a service which gathers the needed information, formats it, and stores it in an output space.  A REST-api should be exposed for client access to the reports.  This feature was suggested by <USER>(NCSU) during a pilot partner meeting on Dec 13, 2010. He was also interested in seeing how the information included in these reports relates to storage costs."
Answer: 293239.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 should disallow updates to the root user security credentials via the REST API."
Answer: 187833.0

User story: The clone() method needs to be implemented in order for "deployedServices" within ServiceManager.java not to have their SystemConfig data member become null after deployment when it is currently going out of scope.
Answer: 3836.0

User story: "This task is to capture all of the audit information relating to storage events for all users in a single location. This listener will be running at all times for all users and storing the results within DuraCloud storage. "
Answer: 688252.0

User story: "This task is to capture and make available to users audit logs which list the activities that have occurred in DuraCloud. There will likely need to be a separate set of logs for storage and services.   Once messaging support has been completed on storage and services, a new service could be created to listen to the messages being sent and store write those to log files which are stored in the user's storage area."
Answer: 908363.0

User story: This improvement should include the following updates to the Bulk Bit Integrity Service: - remove config option from ui/xml: "destination space" - have service output automatically right to the space "x-service-out", with the content prefix "bitintegrity-bulk/" - remove config option from ui/xml: "working space" - have service automatically set working space to "x-service-work" 
Answer: 65339.0

User story: This improvement should update the Bit Integrity Service in the following ways: - create a default space for output - create auto-generated output name - provide checkbox for providing input listing name - add a checkbox for "I do not have an input listing", which cause an input listing to be generated from metadata 
Answer: 11762.0

User story: These changes apply to both the Image Transformer and Bulk Image Transformer services:  - Clarify the "Destination Color Space" such that it is not confused with a DuraCloud space - Move file name prefix/suffix options directly under source space
Answer: 129807.0

User story: "Items to simplify for bulk services (Duplicate on Demand, Bulk Image Conversion, Bulk Bit Integrity Checker):  1. Use a default setting for number and type of instances. The number and type will depend on the service and will require testing to determine a reasonable default. (10 large instances should work for Bulk Bit Integrity, testing by the pilot partners should help narrow in on good defaults for Duplicate on Demand and Bulk Image Conversion)  "
Answer: 100772.0

User story: "Being able to select an alternate deployment location when deploying a service is a feature to come down the road, but in the meantime, the UI should not display this option when none of the services use it."
Answer: 22851.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 observed that, when using DurAdmin, it can be easy to forget which storage provider is selected and perform an action on the wrong provider. This task is to provide a visual cue to help distinguish between providers.   One potential way to do this would be for each storage provider to correspond with a different color, and that color be displayed prominently (perhaps even as the spaces area background) when that provider is selected."
Answer: 89249.0

User story: "It would be helpful if the Sync and Retrieval Tools could report back (perhaps with a percentage counter or asterisks across the screen) on the progress of each upload as it is happening. This additional feedback could be made available via special command-line switch and not be part of the default behavior, as it is only useful when running the tools interactively.  Currently, the tools do provide feedback regarding the number of objects successfully transferred, but there isn't a way to see the progress of very large files that take a long time to upload."
Answer: 3869326.0

User story: "The clean should include: 1. change order of services to be logical (or possibly alphabetical) 2. change name of services in UI to have the same prefix if they are variations on the same service     - example: Bit Integrity Service - Bulk "
Answer: 10197.0

User story: "The clean of the Bit Integrity service should include: - remove 'salt' from UI - split the service into two services:  -- Bit Integrity Tools (generate & compare) -- Bit Integrity (verify)"
Answer: 15081.0

User story: "Move the generation of content checksum from getContentMetadata to addContent.  Also waiting for feedback from the Azure team to find out why they do not provide the md5 in the eTag."
Answer: 28572.0

User story: Currently, when duplicating large content via the duplication-on-demand service, occasionally more than 10 minutes passes during processing so the Hadoop framework assumes the slave node has died. This improvement should add a "progress" update during the duplication process. As possible implementatin could include: - re-add ContentStore to FileCopier - add a new method to FileCopier that uses ContentStore - add a method to RepMapper that is similar to ProcessFileMapper.doCopy() 
Answer: 165864.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: "I think the retrieval tool is missing an option where you can retrieve specific file(s) from a specific space.  So, in the DSpace use case, when doing a partial restore, you may wish to retrieve only a portion of the files from the space (rather than having to pull down all of them).  I would like to be able to request specific files by name (or by a comma separated list of names).  A regular expression could also work, but a list of exact names would seemingly meet the needs for DSpace. So, for DSpace, the AIP files stored in DuraCloud will have very specific names, similar to:  <EMAIL> <EMAIL>  Generally the AIP name is a specific format: <DSpace-Object-Type>@<DSpace-Object-identifier>.zip  So, if a DSpace install wanted to restore just a particular object (or small set of objects), it might be nice if they can request *just* those objects by name (rather than having to pull down their entire space).  I just know this is a specific case that's currently missing -- we either need a simple solution from the Retrieval tool, or we need a DSpace-specific tool to support partial content restores (where a user only wants to restore a particular set of items or a single collection)."
Answer: 1430107.0

User story: "This task will remove the system services (imagemagick, webapp util) from the list of deploy-able services and instead have them be deployed as needed when dependent services are deployed. Likely this will mean bundling the jars for these services into the services for which they are a dependency, and updating them to start when they are deployed into OSGI."
Answer: 274868.0

User story: This improvement should ensure that content that is replicated via the "Duplicate on Ingest" service should also duplicate the user-supplied metadata.
Answer: 9611.0

User story: "This improvement is to change the Bit Integrity Service to leverage the 'mode' schema element to specify the need for resolving spaces for all providers."
Answer: 40414.0

User story: This improvement is to have ServiceManager.java resolve the spaces for all providers when a service config object specifies a "ALL_STORE_SPACES" mode.
Answer: 7392.0

User story: "It is not necessary for the retrieval tool to create a directory for the space being retrieved when retrieval is only for a single space. This task is to update the retrieval tool such that when only one space is being retrieved, the files go directly into the content directory. When multiple spaces are retrieved, space directories are created, as is the case currently."
Answer: 469720.0

User story: "The following flags need to be updated in the sync tool to match the retrieval tool: 1. password: change to -p 2. port: change to -r 3. backup (work) directory: change to -w 4. sync (content) directory: change to -c 5. sync deletes: change to -d 6. exit on completion: change to -x 7. add: store id: -i"
Answer: 20709.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: "Remove the notice that the space needs to be open in order to view the image in the J2K viewer.  Change the link to view closed images in J2K viewer.  Also change viewer url param from http to https.  Make sure to release with issue DURACLOUD-138"
Answer: 3909126.0

User story: "several pilot partners have requested the ability to upload multiple files or folders via the DurAdmin UI interface, as opposed to the single file that they are now limited to"
Answer: 522640.0

User story: "This task is to provide a notification to the user running a service when that service completes. The notification should include (a link to) the final output report, if one was generated by the service.  Original description: <USER>suggested that adding some sort of pop-up, email message, or other indicator might be a good idea once the fixity service has finished the job that it is running. It isn't clear how to tell when it is finished beyond polling the Services page."
Answer: 607926.0

User story: "This improvement is to revisit the hadoop services: - fixity - bulk image conversion - replication on demand  and ensure the content pulled from S3 is valid with respect to its stored MD5 value."
Answer: 4841.0

User story: "This improvement is to update storeclient to have the option to wrap the content input stream with a DigestStream and check against the etag for validity."
Answer: 3924282.0

User story: "DURACLOUD-178 transitioned the majority of the interactions over to using the Amazon-provided java client. Unfortunately, when that work was done, that client did not yet support Cloudfront, so access to Cloudfront continued to be through Jets3t. Once the Amazon library is updated to include Cloudfront, this task is to complete the transition and remove Jets3t from the S3StorageProvider dependencies."
Answer: 3952641.0

User story: "This feature is to create a StorageProvider implementation that caches read requests for content to local storage (EBS, etc) and services subsequent requests from that cache."
Answer: 1414186.0

User story: "This feature is the DuraCloud marker for the Fedora issue: https://jira.duraspace.org/browse/FCREPO-748"
Answer: 28801.0

User story: "Integrate Azure storage as another exposed storage provider within the duracloud platform."
Answer: 3165.0

User story: "This improvement is to allow developers to run the test suites more often by reducing the amount of time it takes to run a build. There are many integration tests that unnecessarily go all the way to the underlying storageproviders. These tests should be revisited with an eye towards mocking out the network calls where they are overly redundant."
Answer: 3981675.0

User story: "This improvement is to create a top-level exception barrier for the durastore and duraservice REST-APIs. Currently, unexpected exceptions appear in the client response as either a stacktrace or a tomcat html error document."
Answer: 4.0