So i cloned mayan-edms, cloned the new version lifespan app (inside the
apps directory), added versions_lifespan to installed apps in settings
base.py, then (inside a virtualenv) i installed requirements and
manage.py migrate and createsuperuser and runserver with settings flag
--settings=mayan.settings.development. everything works (except for
database locks due to using sqlite) but i can't see the edit lifespan
button you showed me in those screenshots in the docuement versions
list. what am i doing wrong ?
On 12/13/15 3:12 AM, Roberto Rosario wrote:
Progress so far:
* Base app
* Model with, separate lifespan (expiration) for each document
version in the system.
* View
* Permission
* Link
* Model tests
* Signal handler
TODO:
* Default lifespan for newly created document versions.
* What to do with expired document versions.
* Finish packaging: setup.py, coverage, docs, Manifest
* Translations
* API endpoint
* View test
* API test
<https://lh3.googleusercontent.com/-y465M_qBtDc/Vm0nRKebNRI/AAAAAAAAlcE/Tj63LCjMRtc/s1600/Screenshot%2Bfrom%2B2015-12-13%2B04-04-01.png>
<https://lh3.googleusercontent.com/-9AOAE3LL5IU/Vm0nHjKTPWI/AAAAAAAAlb8/y0lun82YXSQ/s1600/Screenshot%2Bfrom%2B2015-12-13%2B04-05-51.png>
On Friday, December 11, 2015 at 6:19:24 PM UTC-4, Roberto Rosario wrote:
I've created a project in the gitlab to allow easier
collaboration: https://gitlab.com/mayan-edms/versionlifespan
<https://gitlab.com/mayan-edms/versionlifespan>
On Tuesday, December 8, 2015 at 6:40:40 AM UTC-4, Abdulhakim
Tlimat wrote:
I am trying to implement a new feature, i want to add a
lifespan or an expiration date option to each document version
(some documents will have such feature not necessarily all),
say it's set to 90 days. a notification should be sent to some
users after 90 days, and the document should be marked as
outdated. until the document maintainer login and updates the
document.
Mr.rosario already pointed me to add a separate app to manage
DocumentType to lifespan setting but this does not exactly fit
my needs.
so i decided to modify the DocumentVersion model i added:
|
expirationDate
=models.DateTimeField(blank=True,null=True,verbose_name=_('Expiration
Date'))
versionNumber =models.IntegerField(_('Version
Number'),unique=True)
|
and i want them both to be visible on the Document versions
list but i cant figure out how to add columns to that generic
list template.
here is the view i need modified in Documents app .views
|
classDocumentVersionListView(SingleObjectListView):
|
at later stage i will add a periodic task to check the latest
version of each document if they have expirationDate set and
it's expired. and will notify the document creator
so my questions are:
1. is this a good approach to my problem or there's a better
way to do it (i still need each version to have an expiration
date set to it) ?
2. how do i view the new two fields in the document versions
list ?
thanks all
--
---
You received this message because you are subscribed to a topic in the
Google Groups "Mayan EDMS" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/mayan-edms/kh8piRUB-sM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
