On Mon, 2008-06-02 at 17:16 +0930, Heath Frankel wrote:
> Labels only work on pages, not on attachments.  Are we looking at a page per
> paper or page per conference?  If the former then this suggest could work,
> but I don't think is as good as an index, however much more automated.

My full thoughts on this were:

A main conference index page linked to a single page about the
individual conferences.

On the individual conference page there could be a brief description as
well as dates/times and location of the conference.  Each paper,
presentation, poster, etc. is attached to a child page of this
conference where the author could add the abstract or a brief
description.  This page carries the Labels for the attachment. 

This way only the main conference index has to be maintained by a single
person and future conferences can be added as soon as we know of a
planned openEHR event.  

This gives us everything linked to a specific conference as well as
being able to search for specifically labeled subject matter across the
site.

--Tim
  


-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Displayemail.gif
Type: image/gif
Size: 4274 bytes
Desc: not available
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080602/3b76342e/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080602/3b76342e/attachment.asc>

Reply via email to