Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
Jonathan Rochkind
Is this you? Claim Profile »
2 months ago
in Resolving LSIDs with URL resolvers and CouchDB on fak3r.com
I don't know the context or history of LSID, but the naive question is, why not use one of the existing identifier schemes? If not DOI itself, why not purl.org? What are your requirements that these things won't do for you?
- 2 points
- Jump to »
Rod Page
There's some (perhaps too much) history here, but I guess the arguments have been that DOIs cost money (and we have potentially 100's of millions of things to assign identifiers to ), and PURLs are a bit too close to URLs (i.e., we're used to URLs breaking, even though this is bad). LSIDs also dragged our field kicking and screaming away from XML schema (gack) and towards RDF. The reality is we will need to handle DOIs, LSIDs, and URLs.
4 months ago
in Basic Block Data Decomposition in Perl on Reallywow
How does thread handling work in Perl? Does Perl provide any facilities for it, or are you stuck using the OS system primitives?
1 reply
lbjay
I know nothing of the internals. Superficially I know perl has its own threading mechanism called "ithreads". They're like POSIX threads in a lot of ways, but the key difference is that variables aren't shared between threads unless explicitly requested. Each thread gets a copy of all the current process data.instead.
For example...
use threads;
my $foo = 1;
my $thr = threads->create(\&increment)
$thr->join();
print $foo, "\n";
sub increment {
$foo++;
print $foo, "\n";
}
This is going to print "2" and then "1". If you're used to POSIX threads you'd think the increment() subroutine is ++-ing a $foo shared with the main scope, but it doesn't; the thread increments its own copy. If you want $foo to be shared you have to enabled shared data and also declare $foo differently...
use threads;
use threads::shared;
my $foo :shared = 1;
...
For example...
use threads;
my $foo = 1;
my $thr = threads->create(\&increment)
$thr->join();
print $foo, "\n";
sub increment {
$foo++;
print $foo, "\n";
}
This is going to print "2" and then "1". If you're used to POSIX threads you'd think the increment() subroutine is ++-ing a $foo shared with the main scope, but it doesn't; the thread increments its own copy. If you want $foo to be shared you have to enabled shared data and also declare $foo differently...
use threads;
use threads::shared;
my $foo :shared = 1;
...
8 months ago
in Dynamic OpenURL lookup with document delivery on Family Man Librarian
Interesting. Can you provide more information about what you've done to make the SFX link work more of the time? Because, yeah, anyone that works with SFX knows the links don't work as often as we'd like. So what did you do to improve things?
1 reply
FamManLib
Jonathan,
It's not rocket science or whiz bang stuff unfortunately. We're making two
calls, one to the Journal Subscription API and another to the SFX API. In
addition we are requiring that the user inputs sufficiently complete
metadata. In other words we evaluate the data on-the-fly and will not even
bother with the API lookup if we don't have sufficient metadata to work
with. For instance, if the user neglects to input pages or even just a
start page, then the lookup process won't even proceed.
Steve
It's not rocket science or whiz bang stuff unfortunately. We're making two
calls, one to the Journal Subscription API and another to the SFX API. In
addition we are requiring that the user inputs sufficiently complete
metadata. In other words we evaluate the data on-the-fly and will not even
bother with the API lookup if we don't have sufficient metadata to work
with. For instance, if the user neglects to input pages or even just a
start page, then the lookup process won't even proceed.
Steve
The post is here in the mailing list: http://lists.tdwg.org/pipermail/tdwg-tag/2009-A... and it was provoked after this thread from Nicky: http://lists.tdwg.org/pipermail/tdwg-tag/2009-A... showing the convoluted way things have been working. To me it doesn't sound sustainable, at least not something I'd want to try and sustain.