Title: Message Title
|
|
|
|
That gets tricky. DSpace isn't doing the downloading; it's buried deeply inside the parser. We'd have to pre-parse the document, discover that it needs a schema we don't have, resolve it, and stash the schema away, then hand the document over to the real parser. I suppose there might be a way to break into the process by picking off the proper events. I haven't investigated that. Maybe there's a way to wrap the validator.
But manual downloading is done once. It doesn't seem to me to be an unreasonable burden. Doing it automatically is a minor convenience that quickly becomes pure overhead, because we have to check for new schemas every time but the cache will stabilize almost immediately. It just seems to me like more code than it's worth.
Discuss this on #duraspace in the weekly meeting?
|
|
|
|
|
|
|
From documentation:
"It is recommended to validate all AIPs on ingestion (when possible). But validation can be extremely slow, as each validation request first must download all referenced Schema documents from various locations on the web (sometimes as many as 10 schemas may be necessary to download in order to validate a single METS file). To make m...
|
|
|
|
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
