Kristen Lans

Life is Good!

The EOL Profile Newsfeed contains comments left for its owner by other members, EOL Community invitations, and gathers updates associated with the items in the owner's EOL watch list.

Add a new comment

  • Profile picture of Katja Schulz who took this action.

    Katja Schulz commented on Katja Schulz's newsfeed:

    @Nick Durmuller:

    It's not that simple. This particular case is actually quite complicated. Tricholoma albobrunneum is an accepted species name based on several different sources: http://eol.org/pages/1008934/names?all=1 So we definitely need to have a taxon page for it. BUT in the literature the name has apparently also been applied to specimens representing other species, not just Tricholoma ustaloides but also Tricholoma ustale and Tricholoma batschii. So that's why it's listed as a synonym on each of those pages. We would not want to have all these pages merged together because they do represent different species. It's just that there has been some confusion in the application of names in the past. Also, we would not want to have T. ustaloides, ustale, and batschii listed as synonyms on the Tricholoma albobrunneum page, because there's no record of these names having been mis-applied to Tricholoma albobrunneum specimens. The synonym relationship is not reciprocal here. If what you want is a list of pages on which the name Tricholoma albobrunneum is listed either as a preferred name or as a synonyms, you can do a search and click through to see all results: http://eol.org/search?q=Tricholoma+albobrunneum&show_all=true

    It's important to note that the EOL names infrastructure is much more complicated than that of Wikipedia or other sites that build a single consensus classification. Each EOL taxon page matches names from a series of different sources algorithmically. With that many voices weighing in, you'll never get a fully integrated, consistent taxonomy. The best we can do is to provide a semi-consistent approximation that represents dissenting opinions as faithfully as possible.

    about 18 hours ago

  • Profile picture of Katja Schulz who took this action.

    Katja Schulz commented on Katja Schulz's newsfeed:

    @Theodore Ganea: Unfortunately, we cannot change the subject of an article. Only the provider can do this. Also, the sequence of articles changes based on user ratings, so I don't know which article was first when you looked at the page. But neither of the two Brief Summary articles on that pages is terribly long.

    8 days ago

  • Profile picture of Theodore Ganea who took this action.

    Theodore Ganea commented on "Katja Schulz":

    Katja Schulz, On the page "Equus Zebra", the first article in "Brief Summary" is misplaced. In my opinion, it should be under "Comprehensive Description". I am only an assistant curator, so I don't have the rank to edit articles. Please check out the article. If you think the article should be in "Comprehensive Description" please move the article to "Comprehensive Description".

    9 days ago

  • Profile picture of петя спасова who took this action.

    петя спасова commented on "EOL Curators":

    @Michаel Frаnkis: this is bad...

    21 days ago

  • Profile picture of петя спасова who took this action.

    петя спасова commented on "EOL Curators":

    @Michаel Frаnkis: where is this button.

    21 days ago

  • Profile picture of петя спасова who took this action.

    петя спасова commented on "EOL Curators":

    @Michаel Frаnkis: maybe is some sort of error.

    21 days ago

  • Profile picture of Dana Campbell who took this action.

    Dana Campbell commented on "Beautiful yet boring":

    ??

    26 days ago

  • Profile picture of Dana Campbell who took this action.

    Dana Campbell commented on "Beautiful yet boring":

    ????

    26 days ago

  • Profile picture of Katja Schulz who took this action.

    Katja Schulz commented on "EOL Curators":

    @Michаel Frаnkis: It looks like this field has the wrong display label. It should say "Location" rather than "Location Created." The problem is on our end, not CalPhotos. They are using a field that comes with the following description: "Natural language description of the locality where the resource was collected or created..." We do need a generic field like this because many collections don't discriminate between these two options, i.e., their "location" data are a mixture of information about where a resource was created and where a specimen was collected or even where its native range is. This is unfortunate, but it's a reality. I'll ask for that label to be changed.

    27 days ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    Calphotos information harvest error
    A problem I've found a few times with Calphotos, that the location data is not harvested correctly; e.g. on this item it says "Location Created: Ethiopia", but at the Calphotos original it says "photo location Rheine Zoo, Germany" . . . "animal's place of origin Ethiopia". So the EoL harvester is harvesting the wrong data line as the location.

    Can this be solved?

    27 days ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    @Yan Wong: Thanks! Will do, if I find any.

    30 days ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Curators":

    @Michаel Frаnkis: by the way, I think the lag in the Milvus pictures appearing was simply because the code change means they are updated slightly later in the process than previously. So it should only happen this once. Let me know if you see it happen again.

    about 1 month ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    @Yan Wong: Ah! they've all appeared now, thanks! There's 7 pages of photos now, whereas yesterday there were just 3 pages.

    I'll check soon to see if the subsp. and var. codes are working, too.

    about 1 month ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Curators":

    @Michаel Frаnkis: It might just be a time lag. I see that, for instance, http://eol.org/data_objects/28679751 is still there, which is only in Category: Milvus milvus in flight. Can you give me any examples which used to be there but aren't any more? Any idea if the subspecies & hybrid code seems to be working now?

    about 1 month ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    @Yan Wong: Thanks!

    about 1 month ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Curators":

    Thanks for letting me know. I was going to tell you that the new code for this to work is now in operation (also the code to spot subspecies/ varieties), so if any of this is not working, it's a problem from my/the EoL end. I'll try to sort out what's going on tomorrow.

    about 1 month ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    @Yan Wong: Hi Yan - As Milvus milvus popped up on my newsfeed, I looked at the species, and saw all the pics from https://commons.wikimedia.org/wiki/Category:Milvus_milvus_in_flight have vanished from EoL. So unfortunately, the {{Category:Milvus milvus}} trick isn't working. Any suggestions?

    Thanks!

    about 1 month ago

  • Profile picture of Michаel Frаnkis who took this action.

    Michаel Frаnkis commented on "EOL Curators":

    @Cyndy Parr: The pics are viewable by clicking on 'View source'. They were all from wiki commons and flickr of pics that we already have here, so they could be hidden as duplicates.

    about 1 month ago

  • Profile picture of петя спасова who took this action.

    петя спасова commented on "EOL Curators":

    @Michаel Frаnkis: im not a help,but try asking in the forums how can they fix that...

    about 1 month ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL Curators":

    @Dana Campbell: Thanks for reporting this, Dana, we're looking into it so don't hide them.

    about 1 month ago