Features/Duplicate prevention - Revision history

Nun: /* What it is */

2023-08-28T12:25:48Z

What it is

← Older revision		Revision as of 14:25, 28 August 2023
Line 2:		Line 2:

	Example:		Example:
	~~If you are adding a record to an entity, it would be annoying~~ to ~~later find out~~ that ~~the record already exists. Now you~~ have ~~two records~~ with the ~~same data, but~~ with different ~~DataIDs~~. To prevent this there should be some part of the data in the ~~record~~ that ~~is impossible to~~ exist in another ~~record. An example of this would be~~ the ~~social security number of a person~~. If you are adding a record of ~~a person~~ whose ~~SSN~~ already exists in the system, then the ~~person~~ is ~~certainly~~ a ~~duplicate~~.		A hr-management system is used to hire new employees that have to be registered with information such as name and email address. During this registration mistakes can happen where an employee is registered multiple times, creating duplicates in the system with different system ID's. To prevent this there should be some part of the data from the employee that would not impossibly exist for another employee, such as the email address which by design are unique. If you are adding a record of an employee whose email address already exists in the system, then that employee certainly already exists in the system. Other suitable types of data could be Social Security Numbers or CPR numbers, which are also unique by design. If no such suitable data field is available, two or more fields can be used, so that they in combination constitute a unique value. It is for example unlikely that two people with the same name and same date of employment should exist.

	== Guide ==		== Guide ==

Nun: /* How to do */

2023-08-28T07:37:08Z

How to do

← Older revision		Revision as of 09:37, 28 August 2023
Line 4:		Line 4:
	If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.		If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.

	== ~~How to do~~ ==		== Guide ==
	To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.		To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.

Nun: /* How to do */

2023-08-28T07:36:40Z

How to do

← Older revision		Revision as of 09:36, 28 August 2023
Line 7:		Line 7:
	To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.		To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.

			[[File:Field select.PNG\|thumb\|Picture 1]]
	To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.		To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.
	[[File:Field ~~select~~.PNG\|thumb\|Picture 1]]		[[File:Field advanced toggle.PNG\|thumb\|Picture 2]]
	The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.		The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
	[[File:~~Field advanced toggle~~.PNG\|thumb\|Picture 2]]		[[File:Unique key.PNG\|thumb\|Picture 3]]
	Now enable the check mark as shown in picture 3.		Now enable the check mark as shown in picture 3.
	~~[[File:Unique key.PNG\|thumb\|Picture 3]]~~
	Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.		Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.

Nun: /* How to do */

2023-08-28T07:36:06Z

How to do

← Older revision		Revision as of 09:36, 28 August 2023
Line 8:		Line 8:

	To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.		To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.
	[[File:Field select.~~png~~\|thumb\|Picture 1]]		[[File:Field select.PNG\|thumb\|Picture 1]]
	The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.		The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
	Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.		[[File:Field advanced toggle.PNG\|thumb\|Picture 2]]
			Now enable the check mark as shown in picture 3.
			[[File:Unique key.PNG\|thumb\|Picture 3]]
			Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.

Nun: /* How to do */

2023-08-28T07:33:03Z

How to do

← Older revision		Revision as of 09:33, 28 August 2023
Line 8:		Line 8:

	To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.		To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.
	[[File:~~field~~ select.png\|thumb\|Picture 1]]		[[File:Field select.png\|thumb\|Picture 1]]
	The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.		The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
	Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.		Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.

Nun: /* How to do */

2023-08-28T07:32:38Z

How to do

← Older revision		Revision as of 09:32, 28 August 2023
Line 8:		Line 8:

	To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.		To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.
			[[File:field select.png\|thumb\|Picture 1]]
	The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.		The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
	Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.		Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.

Nun at 07:29, 28 August 2023

2023-08-28T07:29:11Z

← Older revision		Revision as of 09:29, 28 August 2023
Line 10:		Line 10:
	The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.		The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
	Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.		Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.


	* Entity: Check for duplicates
	* Field: Is part of a unique key

	~~Note checks realtime when entering data~~

Nun: /* How to do */

2023-08-28T07:28:08Z

How to do

← Older revision		Revision as of 09:28, 28 August 2023
Line 7:		Line 7:
	To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.		To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.

	To set a field of an entity to be a unique key, go to that ~~record~~ in the back-end		To set a field of an entity to be a unique key, go to that entity in the back-end and select your chosen field as shown in picture 1.
			The unique key feature is an advanced one, which means that you have to toggle the advanced view as shown in picture 2.
			Now enable the check mark as shown in picture 3. Your chosen field is now part of a unique key. If this is the only field with this check mark enabled, then this will be the only key. If you select a second or third field, then the combination of the values of those fields will be the unique key.

Nun: /* How to do */

2023-08-24T14:49:42Z

How to do

← Older revision		Revision as of 16:49, 24 August 2023
Line 5:		Line 5:

	== How to do ==		== How to do ==
			To prevent duplications when records are created, the entity needs to be set up right. Either a single field or a combination of fields need to be designated as being a unique key, meaning that if you attempt to create another record with the same combination of fields, you will be prevented form doing so. This can be some field with inherently unique data or for example the combination of a date and a name, where the chance of another record sharing the same date and name is considered extremely unlikely.

			To set a field of an entity to be a unique key, go to that record in the back-end


	* Entity: Check for duplicates		* Entity: Check for duplicates
	* Field: Is part of a unique key		* Field: Is part of a unique key

	Note checks realtime when entering data		Note checks realtime when entering data

Nun: /* What it is */

2023-08-24T14:27:34Z

What it is

← Older revision		Revision as of 16:27, 24 August 2023
Line 2:		Line 2:

	Example:		Example:
	~~Say~~ you ~~had~~ a ~~management system containing employees~~. ~~These employees~~ have the ~~following information: They have a CV~~, ~~current working details, and last workday~~. ~~If a given employees can~~ be in ~~a few different statuses then each of~~ the ~~fields might not make sense. If an employee~~ is in the ~~process~~ of ~~being hired, then they would not have any current work details or~~ a ~~specific last work day~~. If ~~the employee were~~ in the ~~process of being fired~~, then ~~their CV would not matter. This example illustrates how you might want to hide away certain record fields depending on which status~~ the ~~record currently~~ is ~~in. Status level dependencies are used to solve this problem~~.		If you are adding a record to an entity, it would be annoying to later find out that the record already exists. Now you have two records with the same data, but with different DataIDs. To prevent this there should be some part of the data in the record that is impossible to exist in another record. An example of this would be the social security number of a person. If you are adding a record of a person whose SSN already exists in the system, then the person is certainly a duplicate.


			== How to do ==
	* Entity: Check for duplicates		* Entity: Check for duplicates
	* Field: Is part of a unique key		* Field: Is part of a unique key

	Note checks realtime when entering data		Note checks realtime when entering data