Proposals:Web Storage of data related to mailing list posts: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
Daviddoria (talk | contribs) (New page: = Web Storage of data related to mailing list posts = This page is intended to initiate discussion about adding functionality to the ITK website (possibly based on the MIDAS server) to al...) |
Daviddoria (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
__TOC__ | |||
= Web Storage of data related to mailing list posts = | = Web Storage of data related to mailing list posts = | ||
This page is intended to initiate discussion about adding functionality to the ITK website (possibly based on the MIDAS server) to allow users to store files related to mailing list posts. | This page is intended to initiate discussion about adding functionality to the ITK website (possibly based on the MIDAS server) to allow users to store files related to mailing list posts. | ||
= Benefits = | |||
* When a user reads an old list post, the files will still be available. It should not be the responsibility of each user to ensure all files associated with their posts remain accessible. Even if they don't intentionally remove the files from their webserver, student accounts disappear upon graduation, web hosting services die, etc. so they links may become invalid. | * When a user reads an old list post, the files will still be available. It should not be the responsibility of each user to ensure all files associated with their posts remain accessible. Even if they don't intentionally remove the files from their webserver, student accounts disappear upon graduation, web hosting services die, etc. so they links may become invalid. | ||
= Decisions to be made = | |||
* Image file size maximum - we probably don't want GB images | * Image file size maximum - we probably don't want GB images | ||
* Expiration time (we probably don't need to store them forever, but possibly several years?) | * Expiration time (we probably don't need to store them forever, but possibly several years?) | ||
* Access (some users may not want to publicly distribute all images - but it should usually be possible to create a "demo" dataset that illustrates the point without distributing confidential data to even members of the list (which might as well be considered public?), so maybe not dealing with access could save some headaches? ) | * Access (some users may not want to publicly distribute all images - but it should usually be possible to create a "demo" dataset that illustrates the point without distributing confidential data to even members of the list (which might as well be considered public?), so maybe not dealing with access could save some headaches? ) | ||
Latest revision as of 14:14, 10 August 2009
This page is intended to initiate discussion about adding functionality to the ITK website (possibly based on the MIDAS server) to allow users to store files related to mailing list posts.
Benefits
- When a user reads an old list post, the files will still be available. It should not be the responsibility of each user to ensure all files associated with their posts remain accessible. Even if they don't intentionally remove the files from their webserver, student accounts disappear upon graduation, web hosting services die, etc. so they links may become invalid.
Decisions to be made
- Image file size maximum - we probably don't want GB images
- Expiration time (we probably don't need to store them forever, but possibly several years?)
- Access (some users may not want to publicly distribute all images - but it should usually be possible to create a "demo" dataset that illustrates the point without distributing confidential data to even members of the list (which might as well be considered public?), so maybe not dealing with access could save some headaches? )
