JOIN Case and Document

TMLO in JOIN Case & Document
TMLO number			Element	Mandatory in TMLO	Available in JOIN	Note
1			Entity type	i.v.t.	Yes	The object type in JOIN (document, file, etc.).
2			Identification mark	Yes	Yes	Automatically based on document, file or case number
3			Aggregation level	Yes	Yes	Automatically based on the registration type (dossier, document, file)
4			Name	Yes	Yes	Description field from the registration
5			Classification	Yes	Yes
	5.1		Code	Yes	Yes	Document number, file number or case type code
	5.2		Description	Yes	Yes	Name of collection or of the case type
	5.3		Source	Yes	Yes	Fixed value: JOIN Case & Document
	5.4		Date	Yes	No	JOIN has no information about the validity period of the classification.
6			Description	No	Yes	Can be filled in with second description (such as SUBJECT2)
7			Place	No	No	It is unclear which value is relevant here
9			Coverage	i.v.t.	Yes
	9.1		In time	No	Yes
	9.2		Geographic area	No	Yes
10			External identification features	i.v.t	No	External attributes are not administered in JOIN
	10.1		Feature system	i.v.t	No
	10.2		Number	i.v.t	No
11			Language	No	No	Not administered in JOIN: fixed value is possible
12			Event history	Yes	Yes	Based on audit trail
	12.1		Date / period	Yes	Yes
	12.2		Type	Yes	Yes
	12.3		Description	No	No
	12.4		Responsible officer	Yes	Yes	Username from the audit trail
13			Event plan	No	Yes	Only ‘Destroy’ and ‘Transfer’ based on the selection dates (and removal date)
	13.1		Date / period	i.v.t.	Yes
	13.2		Type	i.v.t.	Yes
	13.3		Description	No	No
	13.4		Reason	No	No
15			Relationship	Yes	Yes	Relationship between document and file (or case)
	15.1		Relationship ID	Yes	Yes
	15.2		Type of relationship	Yes	Yes
15C			(Origin) Context	Yes	Yes	Based on the ‘created by’ field if present
	15C.1		Actor	Yes	Yes
		15C.1.2	Identification mark	Yes	Yes
		15C.1.3	Aggregation level	Yes	Yes	Fixed value: ‘official’, since the actor is the user who created the record
		15C.1.4	Authorized name	Yes	Yes	The username based on the ‘created by’ field
		15C.1.7	Place	No	No
		15C.1.8	Jurisdiction	i.v.t.	No	Not administered in JOIN
	15C.2		Activity (process)	i.v.t.	Yes	The case type or workflow, if available
		15C.2.2	Identification mark	Yes	Yes	The ID of the case type or workflow
		15C.2.3	Aggregation level	Yes	Yes	Fixed value: ‘process’
		15C.2.4	Name of the process	Yes	Yes	Name of the case type or workflow
16			Rights of use	i.v.t.	No	Not administered in JOIN: fixed value is possible
	16.1		Description of conditions	i.v.t.	No
	16.2		Date / period	i.v.t.	No
17			Confidentiality	i.v.t.	No	Is (usually) not administered in JOIN: fixed value is possible
	17.1		Classification / level	Yes	No
	17.2		Date / period	Yes	No
18			Publicity	i.v.t.	No	Is (usually) not administered in JOIN: fixed value is possible
	18.1		Description restrictions	i.v.t.	No
	18.2		Date / period	i.v.t.	No
19			Form	Yes	Yes
	19.1		Editorial / genre	Yes	Yes	Document type, if available
	19.2		Appearance form	i.v.t.	No	Not administered in JOIN
	19.3		Structure	i.v.t.	No	Not administered in JOIN
20			Integrity	i.v.t.	No	Cannot be determined by JOIN: fixed value is possible
21			Format	i.v.t.	Yes	Only for files (records within TMLO)
	21.1		Identification mark	Yes	Yes	Key (GUID) of the file
	21.2		Filename	Yes	Yes
		21.2.1	Name	Yes	Yes	File name without extension
		21.2.2	Extension	No	Yes
	21.3		Type	i.v.t.	No
	21.4		Size	Yes	Yes
	21.5		File format	Yes	Yes	Extension; the translation to PRONOM must be done at e-depot
	21.6		Creation application	i.v.t.	No	Not administered in JOIN
		21.6.1	Name	Yes	No
		21.6.2	Version	Yes	No
		21.6.3	Date of creation	Yes	Yes	Creation date of the file
	21.7		Physical integrity	i.v.t.	Yes
		21.7.1	Algorithm	Yes	Yes	JOIN uses SHA2
		21.7.2	Value	Yes	Yes	Hash value of the file
		21.7.3	Date	Yes	Yes
	21.8		Date of creation	Yes	Yes
	21.9		Event plan format	i.v.t.	No	Not administered in JOIN
		21.9.1	Date	i.v.t.	No
		21.9.2	Type	i.v.t.	No
		21.9.3	Description	i.v.t.	No
		21.9.4	Reason	i.v.t.	No
	21.1		Relationship	i.v.t.	No

¶ JOIN Case & Document is

¶ Elements