Thanks for creating this application. I would like to get some additional details about Seed DMS.
What happens to a document after the expiration period (if it is set)? Does the document get removed from the DMS or does the owner get notified to update the document? It would be great to use this feature to create a review period to ensure the documetn is still up-to-date.
Is there a way to modify the order of the fields presented when you add a new document? For example when a new document is created are the custom fields created always presented at the end of the view or can they be arranged in a specific format? I'd like to have the more important fields presented first.
Is there a way to prevent a document that is not yet in the released state from being visible until it is released?
In addition to these questions, I'd like to evaluate whether thse feature requests are planned or could be implemented and contributed back to the main line of code?
Automatic Document Number Creation and Reservation: We have a document number which is used to identify not only the type of document (Specification or Memo) but also to uniquely identify a document. For example a memo is uniquely identified by the submitters user name (ex: andy.smith-001). A specification is just a number with a prefix (ex: PS-00001, PS-00002, etc).
We will need attachments to be uploaded on a per version basis. Is there a reason this is implemented per document rather than per version?
Are there any current plans to allow a configuration for LDAP connections?
We may need to change the way the revision number is presented. Rather than revision 0, 1, and so on we typically use A, B. This is a lower priority feature.
Thanks,
Rachael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
An expired document just enteres the document status 'expired', that's all. You can still modify, download, delete, .. that document. There is not even a notification. If you need this, you will have to run a cron job which frequently checks for expired documents or those which are going to expired within the next n days.
Not possible
There is some internal mechanism which basically could handle this, but it needs to be fully implemented and I'm pretty sure it turns into lots of diffent cases to be considered.
Your second block of questions:
Can't you handle this with a custom attribute?
There is not specific reason for it.
What do you have in mind? LDAP is basically used for authentication.
Changing the internal version number is crucial, but can't you just map the numeric values on alphabetic values (1=>A, 2=>B, ...) and just change the output of the version number?
Uwe
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for answering the first block of questions. Regarding the second block.
I don't see any documentation on how to implement this with a custom attribute. I see the fields:
Object type:
Type:
Allow multiple values:
Min. number of values:
Max. number of values:
Set of values:
Regular expression:
-Can you give more details on what each of these fields do? For example what does the regular expression field change?
Do you have any pointers on what where I would start to implement a per version attachment change?
For LDAP, I essentially would add an option to the admin dashboard to enable/disable LDAP and if enabled add fields to gather:
AUTH_LDAP_SERVER_URI
AUTH_LDAP_BIND_DN
AUTH_LDAP_BIND_PASSWORD
AUTH_LDAP_USER_SEARCH
AUTH_LDAP_USER_ATTR_MAP
Yes, I would want to just map the ID to another alphanumeric sequence. Could I also do this witha custom attribute?
Thanks for your quick response.
Rachael
Last edit: Rach 2016-02-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To add on to my last post, after poking around some more today, I think I've learned more about how the custom attributes work. It seems the regular expression is just used on the input field when a document is upload. Is that correct?
I tried to integrate LDAP by updating the /conf/settings.xml file. I updated it with the following info <connector enable="true" type="ldap" host="ldap://xxx.xxx.com" port="" basedn="xxxxx" binddn="" bindpw=""></connector>
This not only prevented me from being able to login with the standard authentication method but I was also not able to successfully login with my LDAP credentials. Are there any steps I'm missing to configure this or is this not the right file to update? I noticed that ldap configuration is in the following files:
The regular expression of an attribute definition is just for checking the value of an attribute. The crucial point in your requirement is the 'automatic number creation'. That isn't possible right now.
I guess I can't help with the ldap problem. It's mostly wrong connection settings.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Thanks for creating this application. I would like to get some additional details about Seed DMS.
What happens to a document after the expiration period (if it is set)? Does the document get removed from the DMS or does the owner get notified to update the document? It would be great to use this feature to create a review period to ensure the documetn is still up-to-date.
Is there a way to modify the order of the fields presented when you add a new document? For example when a new document is created are the custom fields created always presented at the end of the view or can they be arranged in a specific format? I'd like to have the more important fields presented first.
Is there a way to prevent a document that is not yet in the released state from being visible until it is released?
In addition to these questions, I'd like to evaluate whether thse feature requests are planned or could be implemented and contributed back to the main line of code?
Automatic Document Number Creation and Reservation: We have a document number which is used to identify not only the type of document (Specification or Memo) but also to uniquely identify a document. For example a memo is uniquely identified by the submitters user name (ex: andy.smith-001). A specification is just a number with a prefix (ex: PS-00001, PS-00002, etc).
We will need attachments to be uploaded on a per version basis. Is there a reason this is implemented per document rather than per version?
Are there any current plans to allow a configuration for LDAP connections?
We may need to change the way the revision number is presented. Rather than revision 0, 1, and so on we typically use A, B. This is a lower priority feature.
Thanks,
Rachael
Your first block of questions:
Your second block of questions:
Uwe
Hello Uwe,
Thanks for answering the first block of questions. Regarding the second block.
I don't see any documentation on how to implement this with a custom attribute. I see the fields:
Object type:
Type:
Allow multiple values:
Min. number of values:
Max. number of values:
Set of values:
Regular expression:
-Can you give more details on what each of these fields do? For example what does the regular expression field change?
Do you have any pointers on what where I would start to implement a per version attachment change?
For LDAP, I essentially would add an option to the admin dashboard to enable/disable LDAP and if enabled add fields to gather:
AUTH_LDAP_SERVER_URI
AUTH_LDAP_BIND_DN
AUTH_LDAP_BIND_PASSWORD
AUTH_LDAP_USER_SEARCH
AUTH_LDAP_USER_ATTR_MAP
Yes, I would want to just map the ID to another alphanumeric sequence. Could I also do this witha custom attribute?
Thanks for your quick response.
Rachael
Last edit: Rach 2016-02-02
Hi Uwe,
To add on to my last post, after poking around some more today, I think I've learned more about how the custom attributes work. It seems the regular expression is just used on the input field when a document is upload. Is that correct?
I tried to integrate LDAP by updating the /conf/settings.xml file. I updated it with the following info <connector enable="true" type="ldap" host="ldap://xxx.xxx.com" port="" basedn="xxxxx" binddn="" bindpw=""></connector>
This not only prevented me from being able to login with the standard authentication method but I was also not able to successfully login with my LDAP credentials. Are there any steps I'm missing to configure this or is this not the right file to update? I noticed that ldap configuration is in the following files:
/install/settings.xml.template_install
./utils/settings.xml
./conf/settings.xml.template
./conf/settings.xml
./inc/inc.ClassSettings.php
I am still
Rachael
The regular expression of an attribute definition is just for checking the value of an attribute. The crucial point in your requirement is the 'automatic number creation'. That isn't possible right now.
I guess I can't help with the ldap problem. It's mostly wrong connection settings.