Resources
Identity Use Cases & Scenarios.
FIDIS Deliverables.
Identity of Identity.
Interoperability.
Profiling.
Forensic Implications.
HighTechID.
D3.1: Overview on IMS.
D3.2: A study on PKI and biometrics.
D3.3: Study on Mobile Identity Management.
D3.5: Workshop on ID-Documents.
D3.6: Study on ID Documents.
D3.7: A Structured Collection on RFID Literature.
D3.8: Study on protocols with respect to identity and identification – an insight on network protocols and privacy-aware communication.
D3.9: Study on the Impact of Trusted Computing on Identity and Identity Management.
D3.10: Biometrics in identity management.
D3.11: Report on the Maintenance of the IMS Database.
D3.15: Report on the Maintenance of the ISM Database.
D3.17: Identity Management Systems – recent developments.
D12.1: Integrated Workshop on Emerging AmI Technologies.
D12.2: Study on Emerging AmI Technologies.
D12.3: A Holistic Privacy Framework for RFID Applications.
D12.4: Integrated Workshop on Emerging AmI.
D12.5: Use cases and scenarios of emerging technologies.
D12.6: A Study on ICT Implants.
D12.7: Identity-related Crime in Europe – Big Problem or Big Hype?.
D12.10: Normality Mining: Results from a Tracking Study.
Privacy and legal-social content.
Mobility and Identity.
Other.
IDIS Journal.
FIDIS Interactive.
Press & Events.
In-House Journal.
Booklets
Identity in a Networked World.
Identity R/Evolution.
Integration in the FCI, Redesign and Functional Enhancements
Until May 2006 the content of the IMS database was moved to the internal FIDIS web site (internal.fidis.net). A first preliminary layout was developed and the integrated content management function used to maintain the content. In total the layout functions were limited by the version of the technical platform (Typo 3) used at that time.
From October 2006 until December 2006 a new version of the platform Typo 3 was developed and introduced by WP1 (JWG). This version enabled enhanced functionality, such as front-end editing functionality, search functions, etc. Based on the work carried out by the FCI Steering Group (with respect to the public layout of the FCI) a new layout for the presentation of the content of the database was developed and tested in January and February 2007.
The following screen shots show the current layout:
Figure : Overview of the available database records
Figure : Example of a sample database record (1/4)
Figure : Example of a sample database record (2/4)
Figure : Example of a sample database record (3/4), zoomed view on a screenshot in a database record
Figure : Example of a sample database record (4/4)
This layout is used for the public deployment of the database on IMS end of March 2007.
For a permanent maintenance structure of the IMS database a content management system is needed. This should support editing of existing records by vendors and the creation of new records. As authentication of vendors and quality of content may be a problem, an editorial check of the content by ICPP is planned. The editing interface needs to support a corresponding workflow to facilitate checking, approving and deployment of new content.
As a first step with respect to described enhanced functionality, an administrative interface for the database was integrated at internal.fidis.net. This interface allows the editing and approving of content by selected editors and supports notification of a selected database manager to stimulate further actions. The notification currently is carried out via e-mail.
The following screen shots show the admin interface.
Figure : Record overview
The admin interface starts with an overview of existing records. Records can be searched for, edited or deleted. When choosing “Edit a record”, the following editing form is displayed (partial view only):
When this form is completed (or changed), a preview can be selected – cp. following screenshot.
Figure : Preview of edited records
The administrative front end is available vial http://internal.fidis.net/community-main/fidis-db/ims-db-admin.
The FCI development work described in this chapter was carried out by JWG, supported by ICPP through description of requirements, testing and approving.
| 6 / 15 |









