Managing content expiration.

Question

Hi everybody!
I am in charge of develop a solution that manages content expiration based on a sort of categories.
I am thinking to do the tasks below:
1- Creating a table in the configuration manager UCM applet and populate this table all category and expiration times.
2- Creating a view that will look for the category table
3- Define this view as a combobox in the check-in form. So, users can choose which category a content belongs to.
4- After calculation, expiration date will be set in dOutDate CHECKIN optional parameter.
Lately, some developers came up with the argument that I could use URM or IRM to manage content expiration.
I'd like to know if my idea is appropriate or it's possible to use URM or IRM to accomplish the task.
Thanks
José.
Edited by: José Márcio Teixeira Júnior on 27/03/2013 17:56

Answer 1

First of all, I think you should approach your requirement from business, or compliance side, not from its technical implementation.
If I read between lines correctly, you want to automate expiration of content (by setting expiration date) based on rules in a custom table (and most likely also the date of its ingestion). If you requirement is really that simple, you may go easily with the functionality of the new component Framework Folders, which introduced Folders Retention - see http://docs.oracle.com/cd/E23943_01/doc.1111/e10978/c08_folders.htm#BCFEHCDJ
Note that retention folders are query folders, i.e. rather "assign" a folder to an item, you can create a query - an item can correspond to several queries at once. And retention rules are a bit more flexible (you may retain x last revisions rather than delete everything, it works with the concept of "fiscal year". etc.)
Records Management (URM, I'd forget about IRM for this case) will be more formal and more complex to setup:
a) it will ensure that content will not be deleted earlier
b) it will keep audit
c) disposition rules can be even more flexible
d)it minds exceptions (so-called "freezes")
etc.