> SwadECommunityPortal > SwadECommunityPortalIssues

Design issues scratchpad

Privacy

Issue:
Information such as an email address is private, how should the portal handle that?

Discussion:
The page and organization descriptions should only contain public information that providers are happy
to see on their normal web site. In this application search-on-email address seems very unlikely so 
privacy through one-way hash doesn't seem to have much added value and will be ignored for now. 
Obfuscation to hinder machine reading (distorted bitmaps etc) while allowing human access fall foul of
accessibility.

There should be an element type "click through" which requires a button push to bring up the view. This is 
not strong protection but can foil simple robots.

There will also need to be hidden system metadata for controlling the black-list/white-list and registering
email to send completed RDF to. This should not be accessible by search or browse over the portal.

History and representation of change

Issue: 
Organization status and structure changes over time (either because the organization changes or
because the context, such as the legal framework, changes). How to represent this?

Discussion: 
One approach would be to have a different resource for the organization and each time interval
and use the ABC-Harmony information model to represent the nature of the transition between adjacent intervals.

Template

Issue:

Discussion: