I had not imagined that Impact story would apply to groups as well as individuals, but it makes great sense.
ImpactStory also operates against an individual’s ORCiD identifier, and I am not aware that a group can also acquire a ORCiD? Also, we have been using the ORCID public API to authenticate ORCID identifies into applications (such as eg an ELN or a digital repository), so that the trust is firm and complete. I wonder how that might be useful for collaborative applications such as eg CDK, JSmol and the like? Would all the contributor’s ORCIDs bee needed? On 14 May 2014, at 11:13, Egon Willighagen <egon.willigha...@gmail.com> wrote: > Hi all, > > some weeks ago I started making an ImpactStory profile for the Blue > Obelisk. May service as back pocket material if you promote the Blue > Obelisk. It's hard to say we do not have impact, and I think we > succeeded in making a change. > > I have followed Figure 4 from the second Blue Obelisk paper, and > listed papers and software hosted on GitHub (no SourceForge support at > this moment): > > https://impactstory.org/BlueObelisk > > If you find your project missing (likely), please send me the DOI or > GitHub URL (please only for top level projects, so I list only > bioclipse.core). > > The ImpactStory page doesn't feature an logo/icon, and this may be a > good moment to standardize on one, and put that on our project front > pages (something that keeps coming up now and then but something we > never all did…) > ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Blueobelisk-discuss mailing list Blueobelisk-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/blueobelisk-discuss
