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

Enhancing the management and exposure of persistent universal identifiers #35

Open
lsetiawan opened this issue Aug 11, 2016 · 15 comments
Open

Comments

@lsetiawan
Copy link
Member

Hi @miguelcleon and @emiliom,

I am currently, enhancing ODM2Admin by displaying IGSN in the Sampling Features change list, and allow one to enter IGSN when creating a Sampling Feature. I have also added a feature to display ORCID for a Person and their affiliation. Additionally, one can enter a person's ORCID within the person add form.

I improved the UI a bit for listing editable item types in addition to those enhancements.

You can follow my changes here: link

Here are some screenshots if you're interested: link

Thanks.

@miguelcleon
Copy link
Member

Cool, I checked out the screen shoots, looks great. Do a pull request when your ready.

@emiliom
Copy link
Member

emiliom commented Aug 11, 2016

Thanks, @lsetiawan. @miguelcleon, it'll probably be another week or more before we're ready to do a PR. But my goal is to have these new features in place to demonstrate from a local / laptop instance at the Montreal workshop.

@miguelcleon
Copy link
Member

sounds good, l'm looking forward to giving it a try @lsetiawan @emiliom

@miguelcleon
Copy link
Member

Hi, how is this coming along? @lsetiawan @emiliom

@lsetiawan
Copy link
Member Author

Hi @miguelcleon, It is coming along great. I'm still doing few tweaks here and there to improve the UI.

@emiliom
Copy link
Member

emiliom commented Aug 17, 2016

Yup. @lsetiawan is now exposing doi's, ORCID id's and IGSN's in a nice and user-friendly way, as links to the external records. I'll show this in Montreal next week. Don should be able to submit a PR next wee, once the code stabilizes and we're less focused on entering the cross-CZO sampling information (for the meeting), thinking through UI implications, etc.

@miguelcleon
Copy link
Member

Thinking about doing a PR today? @lsetiawan

@emiliom
Copy link
Member

emiliom commented Aug 22, 2016

@miguelcleon, I've asked @lsetiawan to hold off until after the workshop. Mostly, b/c I need his time! At the workshop, you and I can chat about the changes Don has made and discussions we've had; I can show them to you on my laptop. Then after coordinating with Don, he can do a PR after Wednesday. Sound good?

@miguelcleon
Copy link
Member

ok

@miguelcleon
Copy link
Member

@emiliom can @lsetiawan issue the PR now I'd really like to see those changes you should role into the site. Thanks!

@emiliom
Copy link
Member

emiliom commented Aug 29, 2016

@lsetiawan was getting set to do that today, but we weren't able to touch base on this today. We'll discuss tomorrow (Tue), and hopefully he'll be able to follow up with a PR or more soon after.

In the meantime, if you're really curious, all his changes are on his fork, on the crossczo branch. At least changes through last Wednesday, which include everything I told you about or showed at the workshop.

@miguelcleon
Copy link
Member

Yeah I was thinking about that, I'd prefer a PR, showing the site again on Wednesday morning so I might pull from it but I don't want to if it's not ready.

@emiliom
Copy link
Member

emiliom commented Aug 30, 2016

Got it. I have no clue how much extra work it'll be for Don to create the PR(s) after he and I talk tomorrow. But hopefully it won't be a big deal, and he'll be able to submit by your mid afternoon, maybe earlier.

@miguelcleon
Copy link
Member

Hopefully shouldn't be a big deal. Thanks!

@emiliom
Copy link
Member

emiliom commented Aug 30, 2016

Don and I discussed the PR an hour ago. He will submit it very soon, if he hasn't done so already. His availability to answer questions this week may be limited, but from what he tells me, the PR has few or no conflicts relative to your master branch, so hopefully you'll be able to merge easily.

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

3 participants