for the work Rob and his team does. Let me offer some insights from a
general web/database design perspective.
What are you talking about is really some kind of asset management system
and some kind of workflow component. Most content management systems let you
upload assets into an asset library which can then be linked to the content
pages themselves. What is needed beyond this (1) is a way to collect useful
meta-data about the asset, such as owner, time-of-upload, where-used etc and
(2) and interface to view and manage all this stuff.
So, with that in mind, I suspect that you'd be hardpressed to find an
'offline' management tool to do this. It is not impossible, but since all
the data is usually captured and stored in the CMS system anyhow, you might
have more luck getting a view created for your CMS, or having something like
FileMaker 'peek into' your CMS's database for that sort of data.
We use Drupal for most of our projects, and take advantage of the workflow
module (amongst others) to help with notifications and expiration.
You can also do this with FileMaker if you can access the database backend
(mysql or mssql). FileMaker (especially FMP10) can be the interface to your
assets meta-data--with FMP you have much richer environment for live reports
and other kinds of reporting/alerting.
Hope this helps
On Thu, Feb 12, 2009 at 11:50 AM, TJ Rainsford <tjrainsford@gmail.com>wrote:
> Lorrie:
> Absent a content management system that can report changes to Web content,
> there are a couple of different strategies you can take but most require a
> fair amount of manual updating. Let me at least offer one potential
> strategy.
>
>
[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a creative commons, attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=ISED-L
