Based on your knowledge of current ECS models will your workflow cross tenant boundaries? If
...
yes the following checklist may help you determine what features you need to create to enable your
...
funcitonality for libraries using ECS.
...
General
- Build a workflow for your feature for non-ecs FOLIO that identifies the objects (Eg. User, order line, request, item etc.) needed at each stage of the workflow
- Identify where the objects (Eg. User, order line, request, item etc.) in your workflow are stored for each ECS model (LC or MOBIUS)created/edit. Are they created by the member library or Central office?
- For each object highlight the "Links" or "References" that object has to other objects
- For each stage of the workflow. Identify the linked objects that are not available in the tenant in which the primary object is stored.
- Consider how the user might manage this linked object with the current design by adding a tenant designation selection to the search or filter .
- Discuss your linked data issue and potential design adjustment with Architecture
- component.
- Create a Jira feature for this functionality and label it ECS"ecs"
Permissions
- Consider whether the object should be editable with permissions from the specific data tenant OR permissions from central tenant. Are there use cases that support allowing permissions to be controlled a certain way?
- What access/permission flexibility is required? Should all users be able to see linked data or only users with permissions in the tenant where the linked data's tenantdata is being stored?
Performance
- This should be similar to considering performance for regular FOLIO.
- Think about how much of it will be done
- How frequently
- How many concurrent users.
- This will certainly be more complicated to test and optimize so leave extra time whenever possible particularly as teams are learning ECS.
...