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 feature for libraries using ECS.
Requirements
- 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)
- 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 to search or filter.
- Discuss your linked data issue and potential design adjustment with Architecture
- Create a Jira feature for this functionality and label it ECS
Permissions
- What access/permission flexibility is required? Should all users be able to see linked data or only users with permissions in the linked data's tenant?
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.
Scalability
- In designing features you must consider first how they will work within a tenant. Scaling up to multi tenant should NOT require significant changes to the user experience.
- What minimal UI changes could you propose for ECS enabled system that would allow users to complete the workflow?