Archive, index and display "archived" news

[Former Member]

Dear all,

<b>My scenario</b>:

Customer creates with XML Forms special campaign news to several reseller chains and displays them in the portal. Campaigns differ according to reseller's chain, so a member belonging to chain A may not see a campaign news item which is displayed to a members of reseller chain B. This is fine.

<b>Customer's wish</b>:

When a news item in this section has reached the status "archived", how to enable users to browse around and display old, archived campaign news for their own chain?

<b>My question</b>:

Does anybody of you at the field know/have heard about a simple archiving solution for XML news items "out-of-the-box" or is custom coding required (we have very limited time and have to use standards & config as much as possible)?

One problem I came around were ACL's; as a default, archived items are displayed only to news creator with "write" access, which of course cannot be granted to users.

Thank you very much for any advice, all responses are hightly appreciated.

Have a nice holidays, all KM's:-)

regs, Anu

[Krasle · Accepted solution]

Hi Anu,

The Lifetime (AKA Time-Based Publishing) feature will allow you to make the news visible for a specific time span to read-only users, but that might not help too much if the "archived" versions have to also be accessible. For this, you would probably need to do a query-based taxonomy with folders for active news and archived news with appropriate queries. This would be in addition to the repository where the news items are actually stored. You would also probably need to set up a metadata property to record the "archived" status.

Maybe there is someone who has already implemented this, since I think it is a common scenario?

Regards,

Darin

[Former Member · Accepted solution]

Hi Darin, thank you very much for your comment! This information is for us important.

- nice regards, Anu

[Former Member · Accepted solution]

Hi Anu, here are some suggestions if you are seeking a more powerful solution to this problem, but this would require custom coding unfortunately.

There are many ways to accomplish this, one of which would be to write a namespace filter that would filter which news items are displayed according to the date, or the iView accessing the folder, etc.

Another method would revolve around coding a repository service that listens to TimeBasedPublish "Stop" events (when a resource has expired), and copies the archived resource to a different folder. If you have dependencies (links to images for example) and you wish to move them along with the news this would pose a problem however, unless you also copy the images and rewrite the links in the news automatically.