| Q1: What about ALIA's server platform and capabilities? |
The host machine is networked into the ALIA National Office system, and comprises (at the time of writing) a 64-bit large-capacity well-endowed state-of-the-art unix-based server, running LAMP (Linux, Apache, MySQL, PHP/Perl/Python), Postfix, Mailman, and assorted other niceties. The service is running 24-hours per day over a 2Mb fibre-optic link to the outside world, with uninterruptible power supplies to all devices. All hardware is reliable and capable, with full maintenance and service contracts on all equipment to ensure that we have minimal interruptions. I'm available at all times via mobile phone or e-mail (see Q17). |
| Q2: How much web space can we have? |
All you need, and for free. The only consideration is that we attempt to minimise traffic so as to benefit low-bandwidth users. Big graphics, flash, and fancy .avi or .mpeg files are best left to hotshot graphic design companies touting their webfarms. We won't limit the amount of what you can place on the site, but you may find limits if you try to go over the top, bandwidth-wise. Your users will complain - or just walk away. |
| Q3: Who looks after the site? Who builds it? |
We offer two models: the first is for small conferences with a small online presence, the second is for conferences that are large and would otherwise swamp our scant resources. Small conferences web pages are generally built by us using the existing ALIAnet template of the day, whilst larger ones are handed over in entirety to the conference committee - with provisos on how far the design and construction can be stretched, and for the whole process to be managed by the conference committee.
If you choose to 'roll your own', then we will still offer advice on design, implementation and directory structure, but in the main we expect that the conference committee will work this one out. No matter which model is chosen, we would prefer to be consulted frequently to discuss design and structure matters, since site performance can be enhanced by good planning, or compromised by lack of attention. |
| Q4: What restrictions are there on content? |
Apart from the provisos mentioned elsewhere in this document, there are no restrictions on content (other than by government regulation): banner ads, images, proprietary file formats such as pdf, Word files, etcetera are all permissible. However... (see next question). |
| Q5: What are the provisos that are mentioned elsewhere in this document? |
ALIAnet is constructed to a standard that information professionals expect. All conference sites must conform to those standards, and with erorr-free html, suitable for access by the widest-possible audience. Style sheets are encouraged to assist in this process. Some of the key points are as follows:
- All text hyperlinks must be underlined;
- All html code must be W3C-validated;
- Access should not be precluded through the use of javascript, java, applets, flash, or other technology;
- All pages must identify the date of modification of the page being viewed;
- Every page must offer an e-mail link for comment, feedback or correction;
- All pages must offer a link to the main ALIAnet home page [http://alia.org.au];
- Page names must be logical and appropriate, with NO spaces in filenames;
- Broken links must be repaired promptly;
- All code must be properly commented where appropriate; and
- All pages must have suitable navigational elements, including links back to the conference's home page.
Overall, the entire conference site should conform to the guidelines set out at http://alia.org.au/alianet/technical.notes.html. Please note also the importance of placing links back to the ALIA home page AND to all pages on the conference site: if this is not done, then ALIAnet's search engine will fail to pick up either the entire site (in the former case) or the page with no link references (in the latter case). |
| Q6: How do we ensure that everything is working okay, regardless of which site design option we choose? |
Whilst we place no restrictions on the design or implementation of the website, it is a requirement that the designer and maintainer develop a close working relationship with the ALIAnet web manager, to ensure that the site functions correctly for delegates and visitors to the site.
In the longer-term, all remaining web pages will be archived on ALIAnet for future access, and because of this, the site will revert to ALIA National Office control and maintenance after the close of the conference program. Therefore, the site must be built to allow for longer-term maintenance. |
| Q7: What about upload frequency, and control? |
Depending on the model chosen (self-service, or maintained and built by ALIA National Office), we offer for the self-managed sites direct access via ftp and/or ssh, or for the sites managed by ALIA National Office, web-based forms which we then process and upload.
If using the self-service model, you can upload, modify, delete and otherwise play with your site as often as you wish, at any time of the day or night. If you have handed over the management of the site to ALIA National Office, then we update the pages as per our normal working program across the site. Of course, we try to update time-critical pages (and revenue earners!) as quickly as we can, and have a priority service for conference websites, regardless. |
| Q8: Who makes modifications to the site? |
If you choose the self-service option, then the person who is handed the keys to the door is responsible for all modifications: regular ALIA National Office staff are not authorised to make alterations. If a dire emergency arises, or if our log files show problems that compromise site performance, the website manager will step in to resolve the issue. If, on the other hand, you choose to have the 'template' model, managed by ALIA National Office, then any or all of the web publishing team might be involved with the site maintenance. |
| Q9: Where will the website actually sit? What will the home URL be? |
There are appropriate locations on ALIAnet for all conferences, from the major biennial to the smaller regional conferences. The pattern is obvious to those who have run conferences in the past, and we try where possible to follow the same naming schema across the conferences website.
If in any doubt, and wanting to print or otherwise publish literature, the URL, http://conferences.alia.org.au, will always have a link to your website.
Under no circumstances are any ALIA conference websites to use anything other than the 'alia.org.au' domain. This is partly for ALIA branding purposes, but is also for legal reasons. |
| Q10: What links can I have? |
Entirely in your court. You may choose to link to external or internal sources. If building your own design, we would prefer that you consider in your design suitable navigational aids, and insist on a link back to the parent site (ALIAnet). Broken links are your responsibility, but we may intervene to repair the link if the overall site performance is compromised. |
| Q11: How long will the conference pages or site exist? |
It will stay on-site until Bill Gates becomes president of Australia. Or longer. Our archival policy is to keep anything, regardless of merit. Hence the desire for locating the conference at the right URL in the first place, to allow for future development, and in having good, clean, code. |
| Q12: What about back-ups? |
If the site will be built and maintained by outside sources, the conference committee should ensure that a copy of the entire conference directory is kept off-site, and in a location that allows material to be recovered in the event of overwriting existing files or other catastrophes. Once the site becomes archival (and moves elsewhere as indicated elsewhere), we will keep a copy in-house. If the site is to be managed by ALIA National Office, a copy is automatically kept in-house. |
| Q13: What extras can you offer? |
All conference pages have access to all current cgi scripts to allow searching, redirecting of mail, forms, surveys etcetera. Password access to 'hidden' files and directories is also possible. By liaison with the website manager, a customised search tool can be built to incorporate into the non-template sites.
We are happy to liaise with committee members about any problems encountered with html scripting, but we are not offering to write specialist scripts. Please note that the site is unix-based, and wherever possible, we deploy tried-and-tested open-standards software with the intent of delivering to the broad masses without special end-user requirements. Therefore, we do not cater for niche software or specialist applications, nor do we wish to embark on a licencing model for software that may not survive in the marketplace long enough to recoup our costs.
In the near future we intend to offer secure services for the processing of financial transactions, but in any event it is a simple matter to link to an outside and secure conference organiser's site for this type of activity. |
| Q14: What about a personalised e-mail account? |
An ALIAnet e-mail account (or accounts) is immediately created for all conferences, and for the life of the conference is redirected to any existing e-mail account anywhere in the world, to a suitable member (or members) of the committee or PCO. This is advantageous for professional conference organisers (PCOs), since we can redirect a generic '@alia.org.au' address to anywhere, at will.
We prefer that all publicity material use this address rather than that of the PCO, since we are then better able to redirect traffic at appropriate times, such as post-conference, when PCOs have long departed. Additional e-mail accounts for specific purposes are also easily added. PLEASE use this facility to organise communications, both in the short- and longer-term. |
| Q15: How about a discussion list (e-lists)? |
An electronic discussion list service (e-list) is available for all conferences. We can create speakers online discussion lists, pre-conference committee e-lists, conference information broadcast lists (open or closed, restricted or not), and any other type of distribution list deemed useful to the conference. Again, at no cost to the conference committee, and as many as you need. |
| Q16: Do you have a Chat service? |
Yes. http://alia.org.au/alianet/chat/. |
| Q17: Where do I go for technical support? |
Although we do not offer 24-hour technical support, we will ensure that the site is fully-operational for the life of the conference, and will take whatever steps required to ensure that the site is accessible and functional during normal working hours in the lead-up to the conference, and at all times during the conference itself. The website manager is personally available via mobile phone at all reasonable hours (0418 244 259), and can respond to issues quickly even when out of the office. |
| Q18: What about archives? |
As mentioned elsewhere in this document, we archive all conference websites AFTER the conference is over. We ensure that all papers and proceedings are kept online, though if papers are presented in non-html or plain text format (such as Word documents, Powerpoint or even PDF format), then they are converted to plain text, usually with considerable time and effort, and generally to the detriment of the paper in question. |
| Q19: Do you have a forum-style service? |
Yes. http://forums.alia.org.au/. |
|
back
