Use ISSN-L as unique identifier

[ppKrauss]

Nice project! I arrived here by http://www.oaspectrum.org/faq ... So, an aleatory-user can suggest and, if appropriate, to collaborate?

For the moment a suggestion: to use ISSN-L the journal unique ID. See explanations at Wikipedia. For future: I can help to adapt here a good ISSN-L Resolver and its database.

[cameronneylon]

Hey Peter

Nice to hear from you. Hope things are well. The driver behind the identifier selection here was primarily what information we had to hand. There wasn't really a resolver for ISSN that we had at the time. So adapting one would be great.

Ana is working on other things at the moment so there hasn't been any active development on the project for a while. I've wanted to get back to it and fill in some gaps and do some analysis but I haven't had time for ages. If you were interested in taking it further maybe we could chat about ways that might be done? It's a nice toolchain and would be good to push some analysis through it, maybe get it published even.

Cheers

Cameron

[ppKrauss]

Thanks @cameronneylon

(...) The driver behind the identifier selection here was primarily what information we had to hand.

The ISSN-L is the best choice, but any other ISSN of the metadata ("information we had to hand") is a reasonable identifier and a reference to ISSN-L conversion... And perhaps more than 50% of used ISSN's are already the ISSN-L's, not need any change.

Example: in the first 3 journals showed at oaspectrum.org, 2041-2223, 1754-1611 and 1423-0127, only the last have an ISSN-L that is different — its electronic-ISSN is 1423-0127 but its ISSN-L is the print-ISSN, 1021-7770.

If you send to me a CSV file with all IDs (all elected ISSNs) I bring back a column with the correspondent ISSN-L.

(...) There wasn't really a resolver for ISSN that we had at the time. So adapting one would be great.

Ok!

(...) so there hasn't been any active development on the project for a while. (...) If you were interested in taking it further maybe we could chat about ways that might be done?

Ok (!)... Well, I need to learn something more about the OACensus tool project. By other hand, an ISSN-L-Resolver is not a part of the tool, but an independent webservice (ex. maybe issn-resolver.arl.org) used by the tool and any other project, as DOAJ, OASpectrum, etc.

It's a nice toolchain and would be good to push some analysis through it, maybe get it published even.

Good iniciatives (and I need to learn more about OACensus)... I can help better for analysis, than software changes... My main interest is not the terminal tool, but the online lookup service and OAspectrum database: I will like to collaborate with these issues in parallel.

[cameronneylon]

Hi Peter

Maybe it would be useful to have a call and talk about what you want to do
and how all these things inter-relate? That might be more efficient the
most efficient as its a bit complex as various bits went to different
places when I left PLOS.

Cameron

On Wed, Jan 13, 2016 at 8:51 AM Peter [email protected] wrote:

Thanks @cameronneylon https://github.com/cameronneylon

(...) The driver behind the identifier selection here was primarily what
information we had to hand.

The ISSN-L is the best choice, but any other ISSN of the metadata
("information we had to hand") is a reasonable identifier and a reference
to ISSN-L conversion... And perhaps more than 50% of used ISSN's are
already the ISSN-L's, not need any change.

Example: in the first 3 journals showed at oaspectrum.org
http://www.oaspectrum.org/, 2041-2223, 1754-1611 and 1423-0127,
only the last have an ISSN-L that is different — its electronic-ISSN is
1423-0127 but its ISSN-L is the print-ISSN, 1021-7770.

If you send to me a CSV file with all IDs (all elected ISSNs) I bring back
a column with the correspondent ISSN-L.

(...) There wasn't really a resolver for ISSN that we had at the time. So
adapting one would be great.

Ok!

(...) so there hasn't been any active development on the project for a
while. (...) If you were interested in taking it further maybe we could
chat about ways that might be done?

Ok (!)... Well, I need to learn something more about the OACensus tool
project. By other hand, an ISSN-L-Resolver is not a part of the tool, but
an independent webservice (ex. maybe issn-resolver.arl.org
http://issn-resolver.arl.org) used by the tool and any other project,
as DOAJ, OASpectrum, etc.

It's a nice toolchain and would be good to push some analysis through it,
maybe get it published even.

Good iniciatives (and I need to learn more about OACensus)... I can help
better for analysis, than software changes... My main interest is not the
terminal tool, but the online lookup http://howopenisit.org/lookup/
service and OAspectrum database: I will like to collaborate with these
issues in parallel.

—
Reply to this email directly or view it on GitHub
#23 (comment).

[ppKrauss]

Hi! You can use the my username as gmail