Skip to content
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

Request: ability to get author id (PAUSE id) in /release metadata #641

Closed
neilb opened this issue Aug 24, 2012 · 12 comments
Closed

Request: ability to get author id (PAUSE id) in /release metadata #641

neilb opened this issue Aug 24, 2012 · 12 comments

Comments

@neilb
Copy link
Contributor

neilb commented Aug 24, 2012

The metadata section in the results from /release include an author entry, but that's the author string (as might appear in the AUTHOR section in pod, such as 'Neil Bowers neilb@cpan.org', unlike the author entry at the top level, or in /module, which is the PAUSE id of the author.

I'd like to use the metadata.author entry, but for my purposes I need the PAUSE id.

I don't think there's a way I could currently map the author string to a PAUSE id (eg by parsing out the email address and calling metacpan API with the email address), so is this a potential feature for the future? It would be very handy if you could provide pause_id or author_id in the metadata section.

Thanks,
Neil

@monken
Copy link
Contributor

monken commented Aug 25, 2012

I think we shouldn't mess with the metadata content because it's what the dist provides and metacpan shouldn't alter any information in there.

You can search authors by email address: http://api.metacpan.org/author/_search?q=email:onken@netcubed.de

@neilb
Copy link
Contributor Author

neilb commented Aug 25, 2012

I discussed this with a few people on the metacpan IRC channel yesterday. Castaway pointed out http://www.cpan.org/modules/06perms.txt, which has the information i'm after.

You're right, this doesn't belong in metadata, but maybe a different section could be included, which holds maintainers, something like:

maintainers: {
    primary: "NEILB",
    comaint: [ "MST" ,"SOLVE"]
}

This would be empty where a module has no maintainers.

Thanks for the tip on searching by email.

@oalders
Copy link
Member

oalders commented Aug 25, 2012

The 06perms.txt data felt like something which could be included in /distribution

@neilb
Copy link
Contributor Author

neilb commented Sep 24, 2012

I'm assuming that if this is going to happen, it isn't going to happen for a while? I'm about to work on the tools I use to build my reviews, and process 06perms.txt myself. Would obviously be much easier if it was included in the information I'm already getting from MetaCPAN :-)

@ranguard
Copy link
Member

@oalders oalders reopened this Mar 16, 2014
@oalders
Copy link
Member

oalders commented Mar 16, 2014

Have re-opened as I'm hoping to tackle this with @neilbowers tomorrow.

@rwstauner
Copy link
Contributor

I still don't understand the original request.

Have fun!

@neilb
Copy link
Contributor Author

neilb commented Mar 16, 2014

@rwstauner, yeah I don't understand the original request either :-)

The good thing is, I've got a much better idea now of what I should have been asking!

@oalders
Copy link
Member

oalders commented Mar 16, 2014

The permissions work is in the following branch https://github.com/CPAN-API/cpan-api/tree/oalders/06perms

@haarg
Copy link
Member

haarg commented Sep 14, 2014

It isn't clear to me what this ticket is about. Possibly it should be closed and a new issue opened for the permissions API?

@oalders
Copy link
Member

oalders commented Sep 14, 2014

Yeah, I'm going to close this. I've opened a pull requestion for the 06perms branch so that I don't lose track of it. I think it's pretty close to being able to merge. Will rebase etc.

@oalders oalders closed this as completed Sep 14, 2014
@neilb
Copy link
Contributor Author

neilb commented Sep 14, 2014

It isn't clear to me what this ticket is about.

Yeah, when I read the first entry, it wasn't clear to me, and I wrote it! :-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants