gnh1201/seeddms-code
1
0
Fork 0
mirror of https://git.code.sf.net/p/seeddms/code synced 2025-02-06 15:14:58 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

remove some tasks already done

Browse Source
This commit is contained in:
Uwe Steinmann 2017-11-21 06:52:24 +01:00
parent cc8161e353
commit 6e05806447
1 changed files with 0 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
TODO
View File

@ -2,16 +2,11 @@ Show workflow steps after document has been released (keep workflow tab)
Show documents in calendar when they where uploaded.
Add attribute type 'date'
Update comment and date of a review/approval, if the same status is set
again. Currently setting the same status is turned of, because it didn't
have any effect, which is quite confusing if the user can do an operation
which has not the expected result.
Show number of documents that needs care (approval, review, any other action
in a workflog) next to Login/Logout-Menu.
Show message on doc info page if documents expects an action like review,
approval, etc.
@ -34,23 +29,15 @@ Allow to specify fine grained notification (e.g. deleting a document, folder)
Have access rights depending on document status. This will allow to
restrict access when a document is in a workflow or has been rejected.
There are still global variable in class SeedetoDMS_Bootstrap_Style
Settings::searchConfigFilePath() and Settings::getConfigDir() use different
approaches to get the configuration directory.
Show expiration status of documents in document list
Export/Import content as xml (even for subfolders)
Copy folders recursivly
Allow operations like delete, move, approve, etc. on a list of documents
Upload of multiple documents without an applet
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
@ -70,9 +57,6 @@ 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)