I've created a project in the gitlab to allow easier collaboration:
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
>
> class DocumentVersionListView(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 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.
