Opened 11 years ago
Closed 8 years ago
#357 closed defect (wontfix)
Availability of harvest output to VLO
Reported by: | keeloo | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | VLO-4.2 or later |
Component: | VLO importer | Version: | |
Keywords: | harvester, workflow, harvester-workflow | Cc: | teckart |
Description (last modified by )
2013-08-09 00:24:03,570 ERROR
[eu.clarin.cmdi.vlo.pages.ShowResultPage#addCompleteCmdiView:475?] -
Couldn't create CMDI metadata:
The error occurs while the data should be there. Investigate if it in effect is, or that there is some reason data being there cannot be displayed.
Partially mitigated by #754
Change History (16)
comment:1 Changed 11 years ago by
comment:2 Changed 10 years ago by
Component: | VLO web app → VLO importer |
---|
Moving to importer, is due to lack of synchronisation between importer and harvester.
Web app could be changed to deal with this more gracefully in the meantime (Thomas's option 1)
comment:3 Changed 10 years ago by
Owner: | changed from keeloo to keesjan.vandelooij@mpi.nl |
---|---|
Status: | new → assigned |
comment:4 Changed 10 years ago by
Milestone: | → VLO-3.1 |
---|---|
Owner: | changed from keesjan.vandelooij@mpi.nl to Twan Goosen |
Check if this is still an issue
comment:5 Changed 9 years ago by
Milestone: | VLO-3.1 → VLO-3.2 |
---|
Splitting 3.1 milestone. Most open tickets go to 3.2 so that we can have a release on the short term.
comment:6 Changed 9 years ago by
Summary: | VLO web application cannot show meta data → Availability of harvest output to VLO |
---|
more descriptive title
comment:7 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:8 Changed 9 years ago by
Milestone: | VLO-3.2 → VLO-3.3 |
---|
Moved a number of existing VLO tickets to 3.3 milestone
comment:9 Changed 9 years ago by
Milestone: | VLO-3.3 → VLO-3.5 or later |
---|---|
Owner: | Twan Goosen deleted |
comment:10 Changed 9 years ago by
Decided to be put on '3.5 or later' milestone in developer video conference
comment:11 Changed 9 years ago by
Keywords: | harvester workflow added |
---|
comment:12 Changed 9 years ago by
Keywords: | harvester-workflow added |
---|
comment:16 Changed 8 years ago by
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
A new harvesting workflow is in development. In the mid-term, incremental import is a better and now feasible strategy that makes the approach described in this ticket obsolete. Closing this ticket, also because of #754 -> VLO issue #31.
ShowResultPage? fails to generate the "complete CMDI view" (which is just the XSLT-generated part at the bottom of the result page when clicking on "Show CMDI metadata") because the CMDI file (which is loaded from the harvester directory) couldn't be found (the URL returns 404).
Which means: at the time of the last VLO file import this CMDI file existed at the harvester directory, but during the last oai-harvester round it wasn't accessible. Possible solutions: