How to handle Millennium scopes
janusman - April 30, 2008 - 20:24
| Project: | Millennium Integration |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | task |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Millennium divides records into numbered "scopes" which create sections of the catalog (for example, a Scope can collect one or more locations, or one or more item types; for example, the "Main library" scope, or the "Electronic Journals" scope).
Currently the module ignores scopes altogether by issuing searchscope=0 arguments in each URL call (for example, in URLs to unique records like http://example.com/record=i123456&searchscope=0), however this might not be the best, if you want to get holdings information only for a certain scope, or set autocrawl for a certain scope.
¿How should this be handled?
#1
Thinking the simplest is to deal with item locations instead of scopes; the module crawls all items, so the item location can be extracted via XRECORD. The admin could configure which locations to import or ignore.