-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confirm that cmdi file is returned when the HTTP-accept header has “application/x-cmdi+xml” #611
Comments
Works on port 88 with good nginx does not work on bad nginx It is because of nginx directive if ($query_string ~* "format=cmdi"){
rewrite ^/(.*)handle/(.*)$ http://$http_host/server/cmdi/oai-metadata?metadataPrefix=cmdi&handle=$2? redirect;
}
if ($http_accept ~ "(.*cmdi.xml*)"){
rewrite ^/(.*)handle/(.*)$ http://$http_host/server/cmdi/oai-metadata?metadataPrefix=cmdi&handle=$2? redirect;
}
which IS in wiki. (and enables other header values, since regex is used, and other kind of links as well |
add commands to check to Wiki |
add to 8443 nginx as well |
Some Item could have specific CMDI file - during creation the admin upload a cmdi file which will be returned. He need to click on |
@MajoBerger
|
waiting for tests and then review |
Done, works, added to wiki etc. |
Where in the wiki? Post a link here pls |
TODO:
7. Persistent Identifiers - Centres need to associate PIDs (handles or DOIs) with their metadata records.
Individual files (e.g. a text, zip or sound file) can be referred to with either the handle of
the describing metadata record in combination with a part identifier11 or with another
handle.
The text was updated successfully, but these errors were encountered: