Story: Save, Close, Delete | BF Thin Thread

Description

Current situation or problem:

As a cataloger, I need the ability to take certain actions on a resource description in order to complete work on the description and keep the database current. Specifically, I need the ability to 

  • Save work on a resource description

  • Close out a resource description

  • Delete a resource description

  • Publish a resource description

In scope

  • Saving edits done on a resource description

    • Automatic save, or

    • Manual save

  • Deleting a resource description entirely from the database

Out of scope

  • Publishing a resource description into production

  • Saving multiple versions of a resource description

  • Validation rules for a resource description

  • Deleting edges/dependencies

Use case(s)

1. Saving - automatic

  • Given that a cataloger has a resource description open in edit mode

  • Throughout the session the resource description will be automatically saved every 60 seconds

  • Changes made to the resource description will be updated in the database with each automatic save action

  • And a confirmation status is generated

2. Saving - manual

  • Given scenario 1

  • When a cataloger manually saves a resource description

  • Then the resource description is updated in the database at that time, separate from the automatic save

  • And a confirmation status is generated

3. Saving - failure

  • Given scenario 1 above

  • When a save action is sent to the database

  • And the action fails

  • And the system generates an error status for the failed save action

4. Close

  • Given scenario 1

  • And the cataloger elects to close the resource description

  • Then the resource description is no longer in edit mode

  • And the resource description is saved, as appropriate, in the database

5. Delete

  • Given scenario 1

  • And the cataloger elects to delete the resource description

  • Then resource description is deleted from the database

  • And a confirmation status is created

6. Delete - failure

  • Given scenario 5

  • And the delete action fails

  • And the system generates an error status for the failed delete action

 

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Pavel Bobylev June 29, 2023 at 6:48 AM

According to the comment from the UI counterpart ticket https://folio-org.atlassian.net/browse/UILD-10, there is no need to implement extra API on back-end to support auto-saving.

This task simplified to delete API only.

 

Discussed and approved with .

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Citation

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 23, 2023 at 10:59 AM
Updated February 8, 2024 at 7:50 PM
Resolved July 5, 2023 at 1:43 PM
TestRail: Cases
TestRail: Runs