With the decision to adopt Option 2 (separate App using Profiles where possible) for the development of Seasonal Calendars (SC), this (epic) issue looks to add seasonal calendar specific data services on the SC server/app to 'translate' calendar service calls to profiles and local calendar DB calls. (eg: CRUD calendar/season/feature). This issue includes the functional requirements described in the following issues:
50 - which describes some of the calendar information to be stored
51 / #52 - describing the fetch/put of information from the SC management UI, the Profiles collection and the local DB store.
57 - passing the Language tab fields to Profiles/local store as appropriate.
Hi @sbearcsiro and @patkyn - As discussed in Tuesday's standup, I've added #69 Store season information as a child to this issue. I'll put #69 back into the to do column as well.
(estimate: 7 days)
With the decision to adopt Option 2 (separate App using Profiles where possible) for the development of Seasonal Calendars (SC), this (epic) issue looks to add seasonal calendar specific data services on the SC server/app to 'translate' calendar service calls to profiles and local calendar DB calls. (eg: CRUD calendar/season/feature). This issue includes the functional requirements described in the following issues:
50 - which describes some of the calendar information to be stored
51 / #52 - describing the fetch/put of information from the SC management UI, the Profiles collection and the local DB store.
57 - passing the Language tab fields to Profiles/local store as appropriate.
69 - store season information
Note: tasks in this epic need to be aware of: