You are here: Main > KwadroNautNoeito
Proposal for Features in Noeito
Table of content:
Introduction
For the old Translationtool there already existed a feature list. I am composing a new one, with the combination of old existing features, things implemented in the first Noeito version (another attempt to create a usuable translation facilitating
thing and seen in other similar websites (like cucumis.org). To get an easy oversight: have a look at cucumis.org add the possibility to post anonymously, get rid of the forums, send mail to the translationlist in question and voila...
Useful links
Features
- Multilingual user interface
- Dublin Core Metadata see below
- Accounting (users, groups). Certain users can moderate postings (think spam, double, fascist,...), others and anonymous can request and post translations, registered users can claim and edit their translations and requests.
- moderation options -- both articles and comments moderated;
- search by author, topic, title or words in the article/comment body
o Truncation
o Field search
o Boolean algebra
o Phrase search
o incremental indexing (as soon as a new document is posted, it gets indexed, so the index is always up to date)
- set custom article expiration (articles automatically deleted X amount of days after posting eg: announcement for action which will be over..)
- file attachments to articles and comments
- subject topics -- you can create subject categories to group together related articles
- RSS/RDF channel pages (for content syndication) + RSS/RDF channel page generator + channel cache mechanism
- posting of plain text, structured text (wiki- syntax) or html
- posting previews
- customizable HTML filtering
- email - notification for moderators (every article and/or comment)
- email - notification for the author of a posting (every comment)
- subscribe your mailinglist - get emails whenever a posting is made and a regexp pattern is matched
- undo - feature for every transaction
- atom publishing support
- webservice or import/export of data and logic
- search langaugewise: look for articles to be translated into language x
- registered users tell the languages they know and how well they speak it (mother tongue, very good,...) and get accordingly the requested translations that the user is capable of translations into.
- people only get the articles to see which have to be translated or reviewed into "their" language
- add the possibility, when requesting a translation, how well it needs to be translated: eg a press release you prefer to have been reviewed by someone who speaks language XY as their mother tongue but just some line to add to pictures of an action could be done by someone who speaks the language just good without a reviewer.
- track changes
DublinCoreMetadata?
- title
- author or creator
- subject and keyword
- description
- publisher
- other contributor
- date
- resource type
- format
- resource identifier
- source
- language
- relation
- coverage
- rights management
Other things to think about
to top
