Sounds good to me. I think the sub-page for the paper could be an optional thing but the link from the conference page can either go to a sub page or directly to the paper. The sub-page approach also assists with the attachment limit issue (which will need to be administered by someone) and allow comments to be made about the paper or presentation.
Heath > -----Original Message----- > From: Tim Cook [mailto:timothywayne.cook at gmail.com] > Sent: Monday, 2 June 2008 9:49 PM > To: heath.frankel at oceaninformatics.com > Cc: 'For openEHR technical discussions' > Subject: RE: MIE-2008 > > > 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* > **************************************************************
