Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LetoDMS ToDO List
#1
hi Everyone here is what Uwe Steinmann LetoDMS Lead Developer is going to be working on in the next while.

if you feel like you want to add something to this list or remove please reply here.

and if you feel like helping Uwe please reply here as well.

We at Trilex Labs would like to Thank UWE for his hard work and his dedication for making LetoDMS leading edge open source document management system.

Thanks

LetoDMS Admin.

Password forgotten function

Delete document from full text index when document is deleted

Do not show documents which are not reviewed or approved or rejected

installation script:
- user simply unpack the tar.gz in a server folder and access that folder
- on startup if there are installation problems php automatically run the configuration script
- the data folder creation can be automatic (user/password for server) or manual (yet ready folder)
- same for the db and the db user
- db creation (run of create table.sql) shoul control if db is yet filled and control for update to do
- the inc/inc.Setting.php is filled asking user entry
- the script can be used to test installation problem without affecting the current installation

The document state is currently not updated when a user is deleted from users list.
For example user A is the only pending approver for a document, then the document is in draft state.
When A is deleted the document should pass automatically in release status.
This could be done with a new function controlling the existance of all the pending approver/reviewer
and eventually updating the status of the document. This function will be called by user-remove function.

Sometimes in the DB are written messages strings in plain language whose
language depends on the current user and will never be translated.
This can be avoided using only coded messages

The mail language is translated using the current user language but should use
the receiver language (not easy).

In my Documents->all documents there should be two lists: one (the current) with
the user's document, and another with the user's updated document (that's because
one user could have updated a document not owned by himself)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)