Repository navigation
Open
Labels
area: settingsSettings and configurationSettings and configurationhelp wantedExtra attention is neededExtra attention is neededstatus: needs-triageAwaiting initial reviewAwaiting initial reviewtype: featureNew capabilityNew capability
Description
Why
Many congregations that would like to try Unitae already keep their publishers in NW Scheduler. Today they have to retype everyone by hand. For a congregation of 100 publishers, that's the main thing standing in the way of trying Unitae.
What we want
An administrator exports his congregation's people from NW Scheduler and brings that file into Unitae. Unitae creates the publishers with what it can recognise, and shows what it couldn't map. NW Scheduler can export its members as CSV, which is the natural place to start.
Done when
- An administrator with the right to manage publishers can import an NW Scheduler member export.
- The import recognises at least names, gender, contact details, baptism, privileges (elder, ministerial servant, pioneer…) and field service group, where the file has them. It maps them onto Unitae's publishers, roles and groups.
- He sees a preview (who will be created, what was not recognised) and confirms before anything is written.
- Importing the same file twice doesn't create duplicates.
- Nothing is sent outside the instance: the file is processed by the app and not kept once the import is done.
- It's covered by tests with a realistic sample file containing made-up people, as described in the testing guide.
Out of scope
- Meeting history, territories and reports. These can come later, one by one.
- Visiting speakers and congregations. These are a good follow-up.
To settle in this issue before coding
- The exact columns of NW Scheduler's CSV export. A sample export with made-up people, attached here, would help a lot.
- How to match an existing publisher on a second import: by email, or by name and birth date.
Where to look
- Data transfer and its developer notes: the existing
.unitaearchive import, its preview and conflict handling. - Publishers and roles & permissions: what a publisher record holds.
- Row-level security: every write is scoped to one congregation.
New to the project? Start with CONTRIBUTING.md and the development setup.
Metadata
Metadata
Assignees
Labels
area: settingsSettings and configurationSettings and configurationhelp wantedExtra attention is neededExtra attention is neededstatus: needs-triageAwaiting initial reviewAwaiting initial reviewtype: featureNew capabilityNew capability
Type
Projects
- StatusShow more project fieldsWishlist
Activity