Is there a way to set Future status from News Asset Builder, so that editors can have their articles 'appear' and 'disappear' (as per asset listing rules) without setting this from the back end? (or moved to 'archive' folder on a set date/time, or combination of both)
Not quite on the Asset Builder, but you could do this with Triggers directed at News Items created in a particular location.
is this a candidate for a feature request...along the lines of
*News Asset Builder Enhancement
ability to set multiple future assets from the asset builder age
ability to move assets on future dates
while we're at it
ability to upload image and caption to display in news item, align left or right
No, because you can already do all of this with triggers. :) The other feature can be done with a nested asset builder in the news item's simple edit view, and a paint layout to display appropriately.
How would you expose the [change future status] trigger details to the front end news asset builder? Keywords?
I'm thinking of a scenario where an editor might build 3 articles to go live on next Monday, next Tuesday and next Friday, dates selected from the asset builder
Oh, I see. Complete misunderstanding. :) If your possible dates are always semi-stable, i.e. provide the option to make live in 1 to 7 days time, you could do this with create locations. Setup 7 folders, with a trigger directed at each that sets a future status of Live for X days in the future based on the folder, with a future linking of next cron run to the trash. Then, as a news item is created, it is linked into the particular folder (if selected) which triggers the future status, and then is trashed out of the folder on the next run.
Does that make sense?
[quote]Oh, I see. Complete misunderstanding. 
If your possible dates are always semi-stable, i.e. provide the option to make live in 1 to 7 days time, you could do this with create locations. Setup 7 folders, with a trigger directed at each that sets a future status of Live for X days in the future based on the folder, with a future linking of next cron run to the trash. Then, as a news item is created, it is linked into the particular folder (if selected) which triggers the future status, and then is trashed out of the folder on the next run.
Does that make sense?[/quote]
Yep.
So shall I put in the feature request? 
You sure can. :)' /> Funding gets you to the top of the list, as always. <img src='http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/tongue.gif' class='bbc_emoticon' alt=':P
Anybody else who wants to see this feature and is willing to part fund it, drop me a line! Obviously the future status from asset builder feature would included all assets...think of the possibilities....
Cheers Avi
The problem is permissions -- remember, you need Admin permission to make something live, which is why we give the sysadmins the ability to ignore permissions on the trigger. We'd have to do something similar for the asset builder. And, consider how this interacts with workflow -- if workflow is applied, a future status change to Live will fail, because the asset isn't approved. These are the things we'd have to consider.
I still think my folder+trigger idea is a winner. :) What would be really cool is if you could pass a time period to the future status trigger using dynamic parameters. Then, you could add a custom form field to the create layout that adds a particular news item and passes the future status time to the trigger.
Dynamic parameters on all triggers and every asset, hooray!!! One could only dream.
Yes! Freedom for everyone! :)