Bug #10929
OAI virtual sets not working in AtoM
| Status: | Verified | Start date: | 02/28/2017 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Dan Gillean | % Done: | 0% | |
| Category: | OAI-PMH | |||
| Target version: | Release 2.4.0 | |||
| Google Code Legacy ID: | Tested version: | 2.4 | ||
| Sponsored: | No | Requires documentation: |
Description
In feature #8238 we added support for 1 virtual set - top level records. When enabled, the page inclues a link that should take the user to the response, e.g.
http://www.example.com/;oai?verb=ListRecords&metadataPrefix=oai_dc&set=oai:virtual:top-level-records
I have confirmed via the demo site that this worked in 2.3.0. Currently it is broken: any attempt to include the top-level set returns a bad argument error.
History
#1 Updated by Mike Cantelon about 5 years ago
- Status changed from New to In progress
#2 Updated by Mike Cantelon about 5 years ago
- Status changed from In progress to Code Review
- Assignee changed from Mike Cantelon to Nick Wilkinson
PR for CR: https://github.com/artefactual/atom/pull/532
#3 Updated by Nick Wilkinson about 5 years ago
- Assignee changed from Nick Wilkinson to Mike Gale
#4 Updated by Mike Cantelon about 5 years ago
- Status changed from Code Review to QA/Review
- Assignee changed from Mike Gale to Dan Gillean
Fix has been merged to qa/2.4.x.
#5 Updated by Dan Gillean about 5 years ago
- Status changed from QA/Review to Verified
- Target version set to Release 2.4.0
Yay, thanks!