Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Below here a table is shown with the identified changes between ECP and Valghalla, based on tasks and user stories

It is a work in progress !!

Data model is shown here: Data model
Transformation:

In general we should remove:

  • CreatedByOld

  • ChangedByOld

From all data model entities

Action

Name

Link

Data notes

Functionality notes

Remove

Materials
Not needed

/administration/material
/building/details/

Remove

Courses
Not needed

/course

Remove

Rooms
Not needed

/building/details/

Remove

Constituency
Not needed

/administration/structure

Remove

Parish
Not needed

/administration/structure

Remove

Sign

Not needed

/building/details/

Remove

Applications
Not needed

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

Remove

Templates

Not needed

/administration/templates

Investigate

Tag

/administration/category

Decide

Group Type → Team type

/administration/category

New

Validation rules

VALGHAL-131 - Getting issue details... STATUS

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

VALGHAL-238 - Getting issue details... STATUS

New entity and table in the data model.

Reference to the selected validation rules

Show in administration area on same level as election.

New

Special diet

VALGHAL-283 - Getting issue details... STATUS

New entity and table in the data model

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

New

Election committee contact information

VALGHAL-111 - Getting issue details... STATUS

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

Show in administration area on same level as election.

Change

Disctrict → Area

VALGHAL-107 - Getting issue details... STATUS

Add in entity data model

  • Description

Rename to Area in source code

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

Add field for

  • Description (multi line)

Change

Election

VALGHAL-101 - Getting issue details... STATUS

Add in entity data model

  • Description

  • Election type reference

  • Lock date

  • 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

Add fields for

  • Selecting election type (dropdown)

  • Selecting start and end date (calendar for each)

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

Change

Building->Work location

VALGHAL-102 - Getting issue details... STATUS

Add in the entity data model

  • List of necessary TaskTypes

  • List of necessary Teams

  • Work location responsible

Remove in entity data model

  • Category

  • Delivery address

  • Delivery Postal code

  • Delivery Postal place

  • Comment

  • Inactive

  • Can expand

  • Informant needed

Rename to WorkLocation in source code

  • Rename to Work Location

Change

Function → Task type

VALGHAL-103 - Getting issue details... STATUS

Add in entity 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 to TaskType 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 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

VALGHAL-104 - Getting issue details... STATUS

Add in entity 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 to Team 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

  • Fjern oplysninger om arbejdssted 

    • Visiting address information

    •  Building Category

    • Expandable

    • Need of Informant

  • No labels