Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
XL < 15 days
-
Medium
-
XL < 15 days
-
Spitfire
-
-
R1
-
R4
-
R4
-
R2
-
R2
-
R2
-
R1
-
R2
-
R1
Description
As a Folio Administrator
I want to track communications with my library staff, vendors, and students in Folio
in the same manner regardless of app.
Notes are desired to record vendor, staff, and patron correspondences. Notes should be:
- Able to create and assign a note(s) to the following records
- Agreement
- License Records
- Provider Records
- Package Records
- Title/Resource Records
- Can assign the same note to multiple packages, titles/resources
- Can add as many notes as desired
- Proposed Note fields
- Note Type
- Note Title
- Note Details
- Notes Details must allow for large # of characters
- Create/Edit a note should support a date/time created and updated stamp
- Notes UI should support a WYSIWIG
- Allow user to delete a Note
Additional comments
- A Notes helper app was implemented but due to significant defects it was recently disabled. Defining requirements for this feature will require reviewing the helper app to determine at what level does it align with expectations.
- Also several apps have requested/implemented Notes fields. Will need to review and determine if expectations align.
TestRail: Results
Attachments
Issue Links
- defines
-
UINOTES-11 Notes Settings: Allow a user to define Notes type dropdown options
-
- Closed
-
-
UINOTES-12 Assign a note | Display a Notes pop-up
-
- Closed
-
- earliest end is start of
-
UXPROD-1748 Integration of Notes into eUsage
-
- Closed
-
- is cloned by
-
UXPROD-1510 Agreements - Notes Support
-
- Closed
-
- is defined by
-
MODNOTES-93 Improvements: Modify metadata triggers not to use additional colums
-
- Closed
-
-
MODNOTES-94 API Tests - Note type limit
-
- Closed
-
-
MODNOTES-95 API Tests - Note Links Endpoint
-
- Closed
-
-
MODNOTES-96 Check note title and detail limit
-
- Closed
-
-
MODNOTES-97 Modify ModuleDescriptor
-
- Closed
-
-
MODNOTES-99 Migrate the code to folio-service-tools library
-
- Closed
-
-
STCOM-505 (ui-notes) Note edit page
-
- Closed
-
-
STSMACOM-185 Common notes accordion
-
- Closed
-
-
STSMACOM-195 Note view page
-
- Closed
-
-
STSMACOM-197 Create connected component for Note view page
-
- Closed
-
-
STSMACOM-198 Create connected component for Note create page
-
- Closed
-
-
STSMACOM-199 Create connected component for Note edit page
-
- Closed
-
-
UIEH-688 View Note pane header dropdown options | Delete
-
- Closed
-
-
UIEH-690 Provider and Resource Detail Record: Display Notes accordion AND Create a Note
-
- Closed
-
-
UIEH-691 Package Detail Record: Display Notes accordion AND Create a Note
-
- Closed
-
-
UIEH-692 Add tests to check Notes accordion functionality
-
- Closed
-
-
UIEH-693 Provider/Package/Resource: Create a note page
-
- Closed
-
-
UIEH-695 View Note | Pane header dropdown requirements
-
- Closed
-
-
UIEH-696 Provider/Package/Resource: Edit a note page
-
- Closed
-
-
UIEH-698 Provider/Package/Resource: View a note page
-
- Closed
-
-
UINOTES-19 Remove sample strings from `translations/ui-notes/en.json`
-
- Closed
-
-
UINOTES-22 Create a permission: Settings : Configure notes
-
- Closed
-
-
UINOTES-23 Create a permission: Notes: Can assign and unassign a note
-
- Closed
-
-
UINOTES-24 Create a permission: Notes: Can create a note
-
- Closed
-
-
UINOTES-25 Create a permission: Notes: Can view a note
-
- Closed
-
-
UINOTES-26 Create a permission: Notes: Can edit a note
-
- Closed
-
-
UINOTES-27 Create a permission: Notes: Can delete a note
-
- Closed
-
- relates to
-
MODNOTES-49 Notes: assign one or several existing notes to an entity
-
- Closed
-
-
MODNOTES-90 Notes: Change PUT /note-links endpoint to make note domain specific
-
- Closed
-
-
MODKBEKBJ-139 SPIKE: Notes Support (backend)
-
- Closed
-
-
MODNOTES-50 Notes: retrieve notes assigned to an entity
-
- Closed
-
-
MODNOTES-57 Notes: support CRUD operations for note types
-
- Closed
-
-
MODNOTES-59 Notes: Implement GET type collection endpoint
-
- Closed
-
-
MODNOTES-61 Notes: Implement POST new type endpoint
-
- Closed
-
-
MODNOTES-63 Notes: Implement DELETE type endpoint
-
- Closed
-
-
MODNOTES-64 Notes: Support getting notes
-
- Closed
-
-
MODNOTES-65 Notes: Support to GET note by id
-
- Closed
-
-
MODNOTES-66 Notes: Support create new note
-
- Closed
-
-
MODNOTES-67 Notes: Support note update
-
- Closed
-
-
MODNOTES-68 Notes: Support note delete
-
- Closed
-
-
MODNOTES-69 Notes: Support bulk method to add/remove notes from/to an entity
-
- Closed
-
-
MODNOTES-70 Notes: refactor code which interacts with mod-users
-
- Closed
-
-
MODNOTES-71 Notes: Limit the number of note types that can be defined in the system
-
- Closed
-
-
MODNOTES-72 Notes: calculate and return note type usage
-
- Closed
-
-
MODNOTES-74 API Tests for GET /notes
-
- Closed
-
-
MODNOTES-75 API Tests for POST /notes
-
- Closed
-
-
MODNOTES-76 API Tests for GET /notes/{id}
-
- Closed
-
-
MODNOTES-77 API Tests for PUT /notes/{id}
-
- Closed
-
-
MODNOTES-78 API Tests for DELETE /notes/{id}
-
- Closed
-
-
MODNOTES-79 API Tests for GET /note-types
-
- Closed
-
-
MODNOTES-80 API Tests for POST /note-types
-
- Closed
-
-
MODNOTES-81 API Tests for GET /note-types/{typeId}
-
- Closed
-
-
MODNOTES-82 API Tests for PUT /note-types/{typeId}
-
- Closed
-
-
MODNOTES-83 API Tests for DELETE /note-types/{typeId}
-
- Closed
-
-
MODNOTES-84 Performance tests for /notes endpoint
-
- Closed
-
-
MODNOTES-85 Performance tests for /note-types endpoint
-
- Closed
-
-
MODNOTES-86 Not informative Error message on POST note duplicate
-
- Closed
-
-
MODNOTES-87 Spike: Change db schema - Notes are domain specific
-
- Closed
-
-
MODNOTES-88 Note metadata fields are not completely stored on PUT
-
- Closed
-
-
MODNOTES-89 Notes: Change GET /notes to make notes domain specific
-
- Closed
-
-
MODNOTES-91 Notes: Adjust API tests after note schema changes
-
- Closed
-
-
MODNOTES-104 Refactoring: split NoteLinksImpl into fine grained REST / Service / Repository parts
-
- Closed
-
-
MODNOTES-105 Refactoring: split NotesResourceImpl into fine grained REST / Service / Repository parts
-
- Closed
-
-
MODNOTES-106 Provide a way to convert generic database exceptions into more specific ones
-
- Closed
-
-
MODNOTES-108 Failing API tests
-
- Closed
-
-
STSMACOM-188 Note create form
-
- Closed
-
-
STSMACOM-196 Create notes pop-up
-
- Closed
-
-
STSMACOM-207 Notes | Filter notes by Assignment status / Sort by Assignment Status
-
- Closed
-
-
STSMACOM-212 Notes displays as duplicated when user trying to do a lot of searches in notes assigning modal
-
- Closed
-
-
STSMACOM-213 Note create form disabled after creation of note type
-
- Closed
-
-
STSMACOM-217 Notes: When Notes Accordion collapse. Do not display Assign and New buttons
-
- Closed
-
-
STSMACOM-223 Fix notes permissions
-
- Closed
-
-
UIEH-671 Spike: Define Notes frontend implementation approach
-
- Closed
-
-
UIEH-678 Add common notes accordion to Provider, Package, Resource pages
-
- Closed
-
-
UIEH-694 Create a staff note: Pane header dropdown
-
- Closed
-
-
UIEH-717 Cover notes functionality with tests
-
- Closed
-
-
UINOTES-29 Fix "webpack-bundle-analyzer" security vulnerability
-
- Closed
-
-
UINOTES-33 Fix security vulnerabilities reported in handlebars >= 4.1.0, < 4.1.2
-
- Closed
-
-
UINOTES-35 Fix security vulnerability reported for js-yaml < 3.13.1
-
- Closed
-
-
UINOTES-36 Fix security vulnerability for ecstatic >= 3.0.0, < 3.3.2
-
- Closed
-
-
UINOTES-37 SPIKE: Investigate vulnarabilities issues in ui-notes reported by gitHub
-
- Closed
-
-
UXPROD-34 User record notes
-
- Closed
-
-
UXPROD-1511 Licenses - Notes Support
-
- Closed
-
-
UXPROD-1512 ERM Resources - Notes Support
-
- Closed
-
- requires
-
MODNOTES-48 Notes: update note's DB schema to support new fields
-
- Closed
-
-
UIEH-643 Spike: Approach to integrations with other Folio modules/plug-ins
-
- Closed
-