Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:13

    mjy on development

    fix catalog link (compare)

  • 18:09

    mjy on development

    fix browse autocomplete (compare)

  • 18:02

    mjy on development

    update params for nomenclature … (compare)

  • 01:08

    mjy on development

    fix typo register STI for new taxon name… Merge branch 'development' of g… (compare)

  • Aug 21 22:51

    jlpereira on buffered

    Added components (compare)

  • Aug 21 20:53

    mjy on nexml

    wip wip (compare)

  • Aug 21 17:42
    TuckerJD added as member
  • Aug 21 17:42
    TuckerJD added as member
  • Aug 21 17:42
    TuckerJD added as member
  • Aug 21 10:49
    LocoDelAssembly commented on e61cc2d
  • Aug 21 10:47

    LocoDelAssembly on rails6

    Updated gems to use Rails 6 SO… (compare)

  • Aug 20 15:57

    LocoDelAssembly on development

    Fix typo (compare)

  • Aug 20 14:54

    mjy on buffered

    Depiction JSON extensions. Fix… (compare)

  • Aug 20 03:06

    mjy on buffered

    add sqed_depiction flag (compare)

  • Aug 19 21:38

    mjy on nexml

    wip (compare)

  • Aug 19 21:38

    mjy on buffered

    depiction end point (compare)

  • Aug 19 19:23
    mjy labeled #1025
  • Aug 19 19:23
    mjy assigned #1025
  • Aug 19 19:23
    mjy opened #1025
  • Aug 19 19:06

    mjy on buffered

    stub buffered branch (compare)

Matt
@mjy
And is returning false.
@LocoDelAssembly the sandbox should be updated with the API changes we made allowing annonymous access, right?
(made a new token)
Stefan Großhauser
@stegro
that one does not want to work either it seems.
Matt
@mjy
Right.
Checking one thing about the update status of the sandbox...
Aha, I see, it needs to be updated.
So- if you want to practice calls (unfortunately with Lepidoptera names), you could switch to hitting this: https://sandbox.taxonworks.org/api/v1
Luckily we're plannign on updating all the sandboxes today, so if you can stay tuned we'll let you know when that happens- will likely be in around 4 hours. That update will fix the API access issue we see there.
I have to step away for a while- others should be lurking here too, and can start to help, please keep asking questions!
Stefan Großhauser
@stegro
alright, I will leave for now, too (end of day here...) but I'll give it a new try after your works.
Thank you for your time and help @mjy !
Matt
@mjy
Starting to update sandboxes, they might be offline briefly.
Matt
@mjy
@/all @stegro All sandboxes are updated, and the API authentication by project_token= is working.
https://sandcastle.taxonworks.org/api/v1/taxon_names?project_token=tF07vts06-PPek48mFtq4A&name=Gryllus
Stefan Großhauser
@stegro
@mjy https://sandcastle.taxonworks.org/api/v1/taxon_names?name=Gryllus&exact=True&project_token=tF07vts06-PPek48mFtq4A returns stuff like Eumodicogryllus, because of True instead of true in python. maybe that makes sense to allow for on your side?
Stefan Großhauser
@stegro
so the intention is that a reader like me makes a query using one of the simple parameters allowed for by /taxon_names, to obtain a bunch of json data of a not-too-big dataset. I iterate through the pages, to glue the complete dataset together to one piece. Then I apply some nosql-json-querying technique to obtain my subset. Correct?
and as I see, the distribution data, the localised names, images and sounds are, like @mjy mentioned, not (yet) accessible this way. It would be awesome, if they would become so!
Stefan Großhauser
@stegro
And another question: Say I would like to access the orthopterafile. At the moment I can do this because you were so kind to create this kind of mirror on your sandcastle. Somehow this exposes only a project 'orthoptera ...' . However, another one like https://sfg.taxonworks.org/api/v1 exposes lepidoptera data (which I do not even find on the regular species file webpage). What is the relation to taxonworks here? The speciesfile databases are respectively a relational database, somewhere, right? So in order to access them via the taxonworks api, one has to make a (local) clone of the complete thing, or be lucky that someone else provides one? I'd be happy to learn how you intended it.
Matt
@mjy
Hi @stegro. Thanks much for all your testing and feedback, it's super useful for us. We'll consider the True/true. I've added an issue: SpeciesFileGroup/taxonworks#1022. In general if you have suggestions like that feel free to add them there. For reference they could, in theory, also be added to https://github.com/SpeciesFileGroup/taxonworks_api/issues (which in afterthought might have been a better place to do so).
You can use as many parameters as you want (not just one at a time), not sure if that is clear. They are added, for the most part, as logical and (unless otherwise noted).
Your idea is pretty much right on, though in theory we should be tuning the responses to get you pretty much what you need with as few queries as you want. Secondarily parsing the JSON is of course possible too.
You're exactly right about the (vast) majority of available endpoints, they have not yet been exposed to the "api", though they do exist for internal use. We will be prioritizing your use case (given the area, find the specimens, images, and sounds (etc.) in that area), your interactions here pushes us in that direction, and you can also make requests on the issue trackers to further prompt us.
Your last question has more tangents.
Matt
@mjy
  • TaxonWorks is a software package, just like, say "Mesquite", or "PAUP". We don't intend for there to be just one instance out there. TaxonWorks is a web-based researcher workbench, it is not intended to be a set of public interfaces, beyond the API that you are playing with. Users logon to use the native interfaces of TaxonWorks. I can create you sandbox accounts to see this.
  • The SFG will be moving all their past projects (not just from SpeciesFiles, but 2 other major projects, 3i, and mx) from their backend into TaxonWorks. That migration is in the process, and the results of that migration are being exposed in the different sandboxes.
  • The SFG will offer an instance of TaxonWorks (like I said, anyone in theory can serve one up, we go to big effort to help developers do this) as a service to our past users, and to those who are willing to work with us to make it better.
  • All the data from past Species Files (and various other projects, including many new ones) are being movied into this Species File Instance (sfg.taxonworks.org) as they become finalized and OK'ed in the sandboxes. That is the LepIndex data you see, and there will be much more.
  • The SFG will recreate (new) species pages like those you are familiar with using a seperate set of software tools, perhaps doing exactly what you are doing, navigating through the API to build up the pieces, then transform them into HTML.
  • The existing SpeciesFiles are only a tiny subset of what will be in instances of TaxonWorks, both as supported by the SFG, and as supported by other people running a copy of TW.
I hope that helps to clarify the idea.
Matt
@mjy
I should add that one instance of tw can handle many projects. I'll expose some more of the SFs to show you some more tokens so you get the idea.
Stefan Großhauser
@stegro
thank you for the explanation matt. I think I understand a little bit better now.
the /{id} get example shows both a project_id and a project_token. according to the description of the project_id this sounds not right.
Matt
@mjy
Technically it is correct, though it seems redundant. THe use case: If you authenticate with a token then you can access data in projects that are not exposed yet to the API, i.e. "your" data. Those data can come from many projects, not just one. So you can scope your search to just one of those projects.
token == user based access, project_token == project based access
Stefan Großhauser
@stegro
ok, so for now, I can do what it most relevant to me, https://www.pastiebin.com/5d56bc8756dbc
that is extract a tree of some species relevant for me. if in the future distribution or further information becomes accessible, even the better.
@mjy have a nice weekend, and thanks again!
Matt
@mjy
@stegro I love it! Exactly what we want to see possible, mixing scripts and API. Have a great weekend, and thank you.
The web representation here http://orthoptera.speciesfile.org/Common/basic/Taxa.aspx?TaxonNameID=1137758 indicates an ID, but curl -X GET 'https://sandcastle.taxonworks.org/api/v1/taxon_names/1137758?project_token=tF07vts06-PPek48mFtq4A' yields success=false
Stefan Großhauser
@stegro
ok, I see, those IDs are generally not the same.
Matt
@mjy
@stegro You are right. The identiers in Speciei files will be migrated as instances of the class Identifier in TW, not as the primary key to the data in TW. You will ultimately be able to search by identifier string as a param to use the Species File identifier in the API.
Stefan Großhauser
@stegro
orthoptera of germany: https://we.tl/t-UlOqQw3es0 there still are several issues in the graph, like nodes which are their own parent, many species I am not able to query yet, nodes with multiple parents, nodes with a single parent but multiply connected, etc.
Matt
@mjy
@stegro Really wonderful. Do really let us know if you think something in the response that doesn't match the parameter descriptions in the api doc. I'd also be curious to know why there are "many species" that you are not able to query. Is this because the name strings are not matching up?
Are you requesting only valid names? Are you requesting only Protonyms (come to think of it that param is new and we might not have documented it)?
Stefan Großhauser
@stegro
@mjy I don't understand yet, why. I have a list of binomial names, but unfortunately I am not an expert and I do not know how to decide if they are valid. Some of them could well be species groups or even obsolete. I guess if it is difficult to find them, this is a sign ;) . However, one example is isophya kraussii, which looks pretty valid to me, but see the urls above: "Isophya" and "Isophya+kraussii+kraussi" are found using /taxon_names?name=Isophya , but not "kraussii" and not "Isophya+kraussii". Maybe you see why?
Stefan Großhauser
@stegro
(using exact=true always)
Matt
@mjy
@stegro that missmatch might be an issue with the import (nominotypical subspecies), I'll have someone look into it.
You can tell if a name is considered valid if it's id matches the cached_valid_taxon_name_id. If it doesn't, it's invalid, for one or more of many reasons.
Matt
@mjy
activerecord-postgis-adapter has just been updated to support Rails 6, which is fully released
That means we have no blockers, I think, to moving to Rails 6, asside from fixing deprecations etc.
Hernán Lucas Pereira
@LocoDelAssembly
Thanks for the heads up @mjy! I've started a new branch for it to explore: https://github.com/SpeciesFileGroup/taxonworks/tree/rails6
Matt
@mjy
Thanks @LocoDelAssembly. Do you have it added to Travis?