[VUFIND-656] Enable sitemapping of multiple cores/indices Created: 13/Sep/12 Updated: 18/Sep/13 Resolved: 18/Sep/13 |
|
Status: | Resolved |
Project: | VuFind® |
Components: | None |
Affects versions: | None |
Fix versions: | 2.2 |
Type: | New Feature | Priority: | Minor |
Reporter: | Ronan McHugh | Assignee: | Demian Katz |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original estimate: | Not Specified |
Attachments: | first_pass.patch sitemap-dk.patch |
Description |
Hi, as mentioned before, we're looking at exposing a separate Solr core as a module within our main instance. This caused a problem - how do we ensure search engine indexing of this module through a sitemap? This led me to do some refactoring of the sitemap.php tool. I have added a section to sitemap.ini where the user has the option to specify additional indices or cores. The sitemap tool then gathers links for each of these indices. Let me know if you are interested in this, further refactoring might include better separation of the querying and writing aspects of the megamethod. |
Comments |
Comment by Demian Katz [ 09/Oct/12 ] |
I'm attaching a second pass at this functionality (sitemap-dk.patch). I fixed a significant bug (the sitemap page counter wasn't incrementing across indexes, so some of the sitemap files were overwriting each other) and did a bit of cleanup (including changing the "index" config setting to "extra_index" for greater clarity). I'm not going to commit this yet -- I need to think about how it should work in VuFind 2.0. Since Solr connections may end up working a little differently in 2.0, we may need to change the configuration settings for this patch a little bit. I don't want to make this layout official until I'm confident that the 1.x settings can move forward cleanly to 2.0. |
Comment by Demian Katz [ 18/Sep/13 ] |
The VuFind 2 architecture allowed a much simpler design/configuration. See https://github.com/vufind-org/vufind/commit/b60a354d311447cd450cd322782d2523cbdc0a81 for details. |