Frequently Asked Questions (FAQ)
How do we work?
Our focus at EKSA is on designing and developing content rich rich websites and web-based decision support tools which make your information and knowledge more accessible to your customers. Plus they are easy for you to maintain and extend.
We can use your existing content or sub-contract content development to a relevant technical expert.
How do we integrate with your existing website?
There are a number of options for integrating the solutions we develop for you with your existing website. These range from replicating partial url to transclusion to creating templates for receiving information from the RCAT in your own website.
What is the RCAT?
Resource Cataloguing and Management Tool (RCAT). This is essentially a special database that we have developed for cataloguing, organising, linking and managing your knowledge resources.
The information is then exported to your website, Smartphone friendly website, wiki or decision support tool. It can also be exported to CD/DVD or to hard copy.
What is a wiki?
A wiki is a collaborative website which enables users (with permission) to add,
edit and comment on content. Users can add or make changes to content in real time
and see who has made previous changes. All information is securely stored in an online
database and pages in the wiki can be easily rolled back to previous versions if necessary.
Can anyone edit the wiki?
Who views, edits or comments on content in your organisation's wiki can be controlled using
a variety of approaches. EKSA will work with you to work out administration and security requirements meeting
your needs.
Who owns the content?
Your organisation owns the content and outputs. This is no different to a hard copy publication.
EKSA has a number of options available for using the RCAT to expand and maintain your content.
How is content maintained?
Content in your website or wiki can be maintained by your organisation using an easy to use content management system (CMS). We will train your staff in using the CMS and provide ongoing support.