Page History
...
So, for example, if your "dspace.url = http://mysite.org/xmlui" in your "dspace.cfg" configuration file, then the HTML Sitemaps would be at: "http://mysite.org/xmlui/htmlmap"
The generate-sitemaps command
This command accepts several options:
Option | meaning |
---|---|
-h --help | Explain the arguments and options. |
-s --no_sitemaps | Do not generate a sitemap in sitemaps.org format. |
-b -no_htmlmap | Do not generate a sitemap in htmlmap format. |
-a --ping_all | Notify all configured search engines that new sitemaps are available. |
-p URL --ping URL | Notify the given URL that new sitemaps are available. The URL of the new sitemap will be appended to the value of URL. |
You can configure the list of "all search engines" by setting the value of sitemap.engineurls
in dspace.cfg
.
Make your sitemap discoverable to search engines
...
Code Block |
---|
<meta content="Tansley, Robert; " name="citation_author" /> <meta content="Donohue, TimothyTim" name="citation_authorsauthor" /> <meta content="Ensuring your DSpace is indexed" name="citation_title" /> ... |
These meta tags are the "Highwire Press tags" which Google Scholar recommends. If you have heavily customized your metadata fields, or wish to change the default "mappings" to these Highwire Press tags, they are configurable in [dspace]/config/crosswalks/google-metadata.properties
...
- No reliable way to determine OAI-PMH base URL for a DSpace site.
- No standard or predictable way to get to item display page or full text from an OAI-PMH record, making effective indexing and presenting meaningful results difficult.
- In most cases provides only access to simple Dublin Core, a subset of available metadata.
- NOTE: Back in 2008, Google officially announced they were retiring support for OAI-PMH based Sitemaps. So, OAI-PMH will no longer help you get better indexing through Google. Instead, you should be using the DSpace 'generate-sitemaps' feature described above.
T