Page Comparison

Remove

Materials
Not needed

/administration/material
/building/details/

Remove

Courses
Not needed

Remove CourseEntity
Remove CourseOccasionEntity

/course

Remove

Rooms
Not needed

Remove RoomEntity

/building/details/

Remove

Constituency
Not needed

Remove ConstituencyEntity

/administration/structure

Remove

Parish
Not needed

Remove ParishEntity

/administration/structure

Remove

Sign

Not needed

Remove SignEntity

/building/details/

Remove

Applications
Not needed

FieldAlternativeEntity
FieldDataEntity
FieldEntity
FixedFieldEntity
FixedFieldValueEntity
FormEntity
FormFieldEntity
FormPostEntity

Some of this functionality / components might be useful in the communication portion)
Like the RTF component.

RemoveChange

Templates

Not needed

/administration/templates

• Remove Blob storage reference

• Replace with configuration and functionality for file repository mapped to a local file storage

Remove

Electorial district
Not needed, will only use District->Area

Remove ElectoralDistrictEntity

/administration/structure

Investigate

Tag

PersonTagEntity
TagEntity

/administration/category

Decide

Group Type → Team type

GroupTypeEntity
has connection to early voting we don’t need.

/administration/category

New

Validation rules

New entity and table in the data model or as a fixed model (enum or json object) in the code ?
No user should be able to change them.

Reference to a localized string per. entry

• Show in Election type configuration

• Use when assigning a task to a user or when a user assigns a task to him/her self

• Also use when automatically updating the users base data (timer job)

• No interface for configuration, types are fixed.

New

Election types

New entity and table in the data model.
ElectionTypeEntity

Reference to the selected validation rules

Show in administration area on same level as election.

New

Special diet

New entity and table in the data model
SpecialDietEntity

Perhaps reuse category dialog setup and category card from administration if it makes sense.

New

Election committee contact information

New entity and table in the data model, see field fields in figma link on the individual task.
ElectionContactInformationEntity

Show in administration area on same level as election.

Change

Disctrict → Area

Add in entity DistrictEntity data model

• Description

Rename DistrictEntity to Area AreaEntity in source code

Move from structure to administration area on same level as election.

Add field for

• Description (multi line)

Change

Election

Add in entity ElectionEntity data model

• Description

• Election type reference

• Lock dateTask lock days

• Election period start date

• Election period end date

Change in the entity data model

• Active / published → change to status model and supply more values, maybe we need to create an enum for this.

Remove in entity data model

• Constituency dependency

• Create a wizard for new elections creation

• Create copy election option

Add fields for

• Selecting election type (dropdown)

• Selecting start and end date (calendar for each)

• Task Lock (default 4 days)

• Selecting lock date within the selected date range (calendar)

• 
  Supply the default value in the municipal configuration database

New

Election

Automated tasks

• De-activate election

Bound to communications settings

New

Election

All election data except participants is copied to a new election call the same and suffixed with (copy)
Or we could try and reuse the “based on election” functionality.
We need to be able to handle tasks and their date if the election date period is smaller than the one they copy from.
The easiest way of of that is to not touch the date period and then let it be up to the employees to adjust afterwards.

maybe we could write a stored procedure for that ?

New

Web (Declaration of consent)

Maybe a reuse the WebConfigurationEntity if it makes sense

• Should be placed under administration

• Will require Rich text editor implementation, reuse from Web area.
  

Change

Building->Work location

Add in the entity BuildingEntity data model

• List of necessary TaskTypes

• List of necessary Teams

• Work location responsible (user)

Remove in entity data modelin the BuildingEntity data model

• Category

• Deliveryaddress

• DeliveryPostal code

• DeliveryPostal place

• Freetext

• Inactive

• CanExpand

• InformerNeeded

• InformationToContactPerson

• ExternalComment

• Rooms

• Signs

• Materials

• BuildingEventLog

Rename to BuildingEntity to WorkLocation in source code

Remove BuildingEventLogEntity data model

• Rename to Work Location

• Move into to Administration area.

Add fields for

• Task Types (multi select from all available task types)

• Teams (multi select from all available teams)

• Worklocation responsible (list (showing name (link to user) and remove option
  Button to add a new/additional worklocation responsibles

Remove / repurpose fields

• New worklocation

  • Category

  • Delivery address

  • Delivery Postal code

  • Delivery Postal place

  Comment

  • Inactive

  • Can expand

  • Informant needed

Rename to WorkLocation in source code

• Rename to Work LocationWorklocation details

  • Information to contact person

  • Comment

  • Comments shown on external web

  • Event log

  • Rooms

  • Signs

  • Materials

Change

Function → Task type

Add in entity FunctionEntity data model

• Short name / Abbreviation

• Start time (only time not date)

• End time (only time not date)

• Use validation demands (yes/no)

• Send reminder notification 5 days before due date (yes/no)

• Is trusted required (yes/no)

• Guide link

Change in entity data model

• FixedCompensation (is always true) perhaps can be omitted

• StaffingElectoralDistricts should be UsedInDistricts and tie to district instead

Remove from entity data model

• Public Description

• LisaIntegration

• ArchiveIntegration

• CanViewPersonData

• CanViewBuildingData

• SetAsDefault

Rename FunctionEntity to TaskType TaskTypeEntity in source code

• No binding to electoral district

• Rename to Task types

• Move from staffing to administration area on same level as election.

• Use upload functionality from templates page or building details page.

Add field for

• Short name / Abbreviation (single line)

• Start time (only time not date) ex. use the time component from the add course occasion dialog.

• End time (only time not date) ex. use the time component from the add course occasion dialog.

• Use validation demands (yes/no)

• Send reminder notification 5 days (fixed interval) before due date (yes/no)

• Is trusted required (yes/no)

• Guide link (single line)

Remove / repurpose fields

• Public Description

• Fee type (always fixed)

• Can view person data

• Can view building data

Change

Group → Team

Add in entity GroupEntity data model

• Short name / Abbreviation

• Team responsible reference(s)

• Work location reference(s)

Change in entity data model

• Freetext → Description

Remove from entity data model

• ShowExternally

• ShowPersonList

• Rooms reference

Undetermined

• Group Type

Rename from GroupEntity to Team TeamEntity in source code

• Rename to Teams

• Move from staffing to administration area on same level as election.

• Show Short name / Abbreviation in overview table

Add fields for

• Short name / Abbreviation

• Functionality to add one or more team responsible(s) like a dialog where you can search for person

Remove / repurpose fields

• Category

• Show person on external web

• Show person list on external web

• Function

• Amount

Change

User interface

N/A

Show election selection as a drop down in top right hand corner.
Note: If it is a lot of work, we can move it and keep the current feel with opening the dialog, then look at it as we near the end.

New

User interface

N/A

Show a breadcrumb in the solution
If we don’t already have some kind of breadcrumb we could use:
https://www.npmjs.com/package/angular-crumbs
Implementation video https://morioh.com/p/ca769096d74d

New

User interface

N/A

Use either

• Small question mark icon and hover over text

• Hover over text on the UI control it self

New

User Interface

Change

Store data in WebConfiguration table
Use the WebConfigurationEntity

Help icon in top righthand corner

Change

Person → Participant

Add to the PersonEntity data model

• Special diet reference

• Team reference (list)

• Exempt from Digital post (true/false, default false)

• Role

  • Worklocation responsible

    Team responsible

    Reader

• Deceased or Missing (true/false, default false)

• Citizenship (true/false, default true)

• CPRUpdated (Datetime)

Remove from entity data model

• Inactive     

• ExpressionOfInterestApproved

• ApplicationApproved

• FreeText

• Car

• HiddenIdentity

• CourseOccasions

• PersonCourseOccasions

• PersonEventLogs

• PersonTags

• FormPosts

• StaffingElectoralDistricts

Rename from PersonEntity to ParticipantEntity

/person → Add person

Add field for

• Special diet (dropdown)

• Team (dropdown)

• Exempt from Digital post (boolean)

Add button (Lookup participant) next to the Social security number, should use a service to lookup the core participant data.

Remove fields

• Category

• Tag

• Car

• Comment

• Inactive

• Hidden identity

All fields should be “read-only” except:

• Special diet

• Phonenumber

• Mobile Phonenumber

• E-mail

• Team selection

Change

Person overview → Participant overview

We might need to change/adjust the view supplying this functionality

/person

Show fields

• Full name

• Team

• Birthday (repurpose social security number excluding the last 4 digits)

• Assigned to at least one task (yes/no)

• Comma separated list - Task types assigned (maybe repurpose assignments)

Remove fields

• Phone number

• E-mail

• Postal code

• Tags

• Status

Filter changes

• Add

  • Team

  • Digital post

• Keep

  • Name

  • Assignments (TaskType)

  • Status ?

• Remove

  • Social security number

  • Postal code

  • Comment

  • Category

  • Placement

  • Course

  • Education

  • Tags

Change

Person details → Participant details

/person/details/<ID>

Add communication log (reuse event log ?)

Reuse button (Lookup participant) next to the Social security number, should use a service to lookup the core participant data.

Remove:

• Comment

• Eventlog (maybe reuse for communication log)

• Courses

New

Import participants

N/A

Should be a background task, because it could take some time ?

New

Export participants

Might need some minor changes

Ensure report generator / analyze functionality can be used for this.

New

Participants functionality

N/A

Logic for the different tasks are described in the tasks.

Automated tasks

• Deletion of deceased participants

• Deletion of all participants

Manually initiated

• Bulk delete participants

New

Link generator

Add entity “LinkEntity” for link storage

• Id (Guid)

• Type

  • Direct link (to a single task or a single Team and all the task associated with that Team)

  • Complex link (to a filtered view of tasks)

• Value (the necessary information for the external web to show the data

The link will be created in the internal application.

Where the functionality is available we should add a icon / button control to show the link
show eg. https://<url to external web>/link?id=<id (Guid) from DB>
Functionality should be used to build the link where needed and to store the link.
for complex links we could require that the filter / query is saved and that way we will have a reference to point at.

It will be parsed in the external web and should always show a minimum amount of information on a unprotected route in the external web.

A details page should also be in an unprotected route in the external web.

Require login/protected route when “Register” button on task is clicked in the external web.

This functionality is referenced a number of places in the specifications.

• A single task

• A single Team (show multiple tasks)

• Complex / filtered task view (show multiple tasks)

New

External web - Task overview

N/A

• Show tasks from a generated link

• Additional filtering options

New

External web - Task registration

N/A

• Register the task to the participant.

• Require login upon registration.

• Start “new user flow” if participant dies not have a user in the system.