Archive indexing
Tue, 03/08/2010 - 03:41
Hello everyone, I'm a first time user of ProsePoint and the site I am building with it is primarily intended as an online archive for the organization's newsletters going back to 1972, along with new ones as they are released, so I have a couple of questions related to that.
1. The client wants an "interactive index" of the archives with a keyword search capability. Indexing by year would certainly be useful compared to hitting "Next Page" repeatedly, but so far I don't see a way to do this in PP. Does anyone know of a plugin or other way to add this capability?
a. If the keywords are added to each story's meta tags, should that allow the standard search box to satisfy the "keyword search" capability they are asking for?
2. When creating editions, I've noticed that the year field in the scheduler only goes back as far as 2007. As I mentioned, I need archived newsletters going back to 1972 to be indexed in proper date order. Is there any way to expand the year field backward so I can retroactively post editions before I was born?
Hi,
> 1.
You could try drupal.org and see if any modules might suit your purposes, but I doubt it. Since what you're asking for sounds quite specialised, it's unlikely that a generic module to do this exists.
If you can't find something suitable, you could consider commissioning us to write up a custom module for you that does this.
> a. If the keywords are added to each story's meta tags,
> should that allow the standard search box to satisfy the
> "keyword search" capability they are asking for?
I'm actually not sure, but I suspect not. The standard search function only indexes the visible content of a node (ie. story), and meta tags may not be included ... but this question is probably better directed towards whatever module you are using to insert meta tags.
> 2.
Visit .../admin/content/node-type/edition/fields/field_schedule on your site and look for Years back and forward.
BUT ...
I think you're asking the wrong question. The Schedule for field only affects when editions are displayed. If you have an edition in the past which isn't going to be scheduled for appearance in the future, it doesn't matter what the Schedule for value is. It makes no difference whether this field is 2009 or 1930 - the Schedule for field behaves the same in either case.