Changes between Version 80 and Version 81 of BluePrintVITA


Ignore:
Timestamp:
03/28/10 13:43:36 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintVITA

    v80 v81  
    9494  is a compliant set - it contains the "Entity" (pfif:person), "Distinction" (pfif:person_record_id, pfif:first_name, pfif:last_name), several "Findings" (pfif:sex, pfif:date_of_birth, pfif:age, pfif:photo_url) and plenty of "Evidence" (pfif:author_name, pfif:source_name, etc.).
    9595
     96== Files ==
     97
     98All data sets describing one and the same instance of a person entity form a '''file'''.
     99
     100For disambiguation, files are sometimes also called '''case'''s.
     101
     102=== Central Access ===
     103
     104All data in a file must be accessible from a central point within the application (the "repository"). Especially the following must be implemented:
     105
     106  - status of the file as a whole
     107  - opening/closing the file for write access
     108  - permanent removal of the file as a whole from the repository
     109  - a directory of all available record types in that file
     110  - export of a file as a whole
     111  - import of a file as a whole
     112  - merging of files
     113
     114=== File Level Auditing ===
     115
     116VITA implementations must be able to log all successful attempts to access and/or manipulate data in a file, even if the application does not require auditing. All logs, regardless of their actual granularity, must be available as a function of the file.
     117
     118Data which will naturally change over time (e.g. the location of a person) must be version-tracked in such way that they can be reconstructed for any point or interval of time.
     119
     120Data which will only change upon administrative measures (e.g. names) do not need to be version-tracked, with the exception of identities.
     121
     122==== Status ====
     123
     124VITA implementations must be able to handle status information of a personal data file as a whole.
     125
    96126== The Data Model ==
    97127
     
    107137
    108138=== Files ===
    109 
    110 All data sets describing one and the same instance of a person entity form a '''file'''. Within a file, data must be consistent, especially there must be only one entity for each (atomic) feature.
    111 
    112 ==== Status ====
    113 
    114 VITA implementations must be able to handle status information of a personal data file as a whole.
    115139
    116140==== Roles ====