-
Hi nesf,
it could be that the 'fopen()' function has been disabled on your server. For further info please see the bottom of this forum post:
[slow loading of main page on Debian etch][1]
[1]: https://sourceforge.net/projects/refbase/forums/forum/218758/topic/2735943
If you cannot enable the 'fopen()' function on your server (due to security concerns etc), and/or don't want to hack...
2009-11-03 23:01:38 UTC in refbase - Web Reference Database
-
Hi MZ,
your observation is correct, tables 'refs' and 'user_data' hold all the relevant data. Table 'refs' is for "global" data (i.e. data that's generally visible to everyone).
Table 'user_data' holds the "user-specific" information, i.e. information that's unique to each user and that can be only viewed & queried by its owner/creator (well, there are a few...
2009-09-18 22:49:27 UTC in refbase - Web Reference Database
-
msteffens changed the public information on the refbase - Web Reference Database project.
2009-09-18 22:26:26 UTC in refbase - Web Reference Database
-
msteffens changed the public information on the refbase - Web Reference Database project.
2009-09-18 22:24:53 UTC in refbase - Web Reference Database
-
Martin, sorry I didn't realize that PMID import is working for you correctly.
I'm not sure what could cause your issue. Have you tried to URL encode the '$crossRefReqDat' data, like this:
$sourceURL .= "&pid=" . rawurlencode($crossRefReqDat);
Also, it's probably a good idea to also apply the fix for the DOI import failure mentioned in my previous post.
Matthias.
2009-09-17 09:53:43 UTC in refbase - Web Reference Database
-
@bizdelnick and @mathfield, regarding the DOI import failure, I've posted a fix in this forum thread:
[DOI import error][1]
@killaqueen/Martin, Knut is probably right that the 'fopen()' function has been disabled on your server. For further info please see the bottom of this forum post:
[slow loading of main page on Debian etch][2]
[1]...
2009-09-17 09:42:23 UTC in refbase - Web Reference Database
-
Sorry for the messed-up code, the Sourceforge Markdown parser (and its preview) still seems to be quite buggy, it certainly does not adhere to the Markdown format… :-(
The XML entities in the above code must be decoded, of course. I.e. " ; (sans the space) should be ", < ; should be <, and > ; should be >.
Matthias.
2009-09-17 09:17:21 UTC in refbase - Web Reference Database
-
Hi MZ,
your analysis is correct, thanks for the report. It seems as if CrossRef did adjust their XML output recently. They've added an XML declaration and added namespaces & other attributes to the `<doi_records>`and `<doi_record>` tags. Also, the first (root) tag contains a newline character in its opening tag. Together, this caused the split pattern to fail.
To fix this...
2009-09-17 09:07:43 UTC in refbase - Web Reference Database
-
Hi Knut,
for a UTF-8 based database, use `utf8_general_ci` in both cases (i.e. for the database collation as well as for the server's connection collation).
HTH, Matthias.
2009-09-17 06:41:00 UTC in refbase - Web Reference Database
-
Hi Cindy, you're welcome.
Yes, I'd be interested in your beginner's tutorial. You can email it to msteffens -at- refbase -dot- net.
Thanks, Matthias.
2009-09-16 23:52:41 UTC in refbase - Web Reference Database
