There are a number of different issues being discussed here and it would be good to lay them out separately.
Even if the process has no problems at all, it can potentially take 6-8 weeks from the time your observation qualifies to the time the badge appears.
The whole pipeline goes something like this:
- your observation must be Research Grade, which broadly speaking means it must have an agreed-upon taxon, and it must not fail any of the data quality items (must have accurate date/location, etc.)
- regardless of the photo/sound license, the observation itself must be licensed for GBIF: CC0, CC BY, or CC BY-NC
- once a week, iNat generates an export for GBIF, so that can add up to a week if you just missed a cutoff (which I believe is on Monday)
- approximately once a week, GBIF ingests the exported data – they’re not always consistent, so this sometimes takes longer; you can see the ingestion history here (as an example, GBIF is doing maintenance this week and the most recent iNat ingestion is actually 12 days old)
- monthly (per Tony), iNat reads back in the data from GBIF and creates “outlinks”, the return links/badges from iNat to GBIF
- specifically for the stats/Year in Review, after you first generate the page, the numbers do not automatically update unless you choose “Regenerate Stats” near the bottom of the page
To see your observations which pass steps one and two, you can go here: https://www.inaturalist.org/observations?license=cc0,cc-by,cc-by-nc&quality_grade=research&user_id=YOURUSERLOGIN
If you want to see if your observation made it to the most recent iNat-generated export (step three), you can find it here, WARNING: this is a very large file and you won’t be able to manually open and inspect it without specialty software
To see your observations which have been ingested into GBIF (step four), go here: https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by=YOURUSERNAME
Note that GBIF search is on the username, not the user id or user login (as an example, Tony’s iNat user login is tiwane, and his username is Tony Iwane, so his GBIF records are under https://www.gbif.org/occurrence/search?dataset_key=50c9509d-22c7-4a22-a47d-8c48425ef4a7&recorded_by=Tony Iwane)
(Edit: added a feature request to make GBIF searchable by iNat user id.)
If you want to see the most recent export generation date and the most recent ingestion date, you can go here: https://www.gbif.org/dataset/50c9509d-22c7-4a22-a47d-8c48425ef4a7#registration
“Publication date” is the export generation date and “Metadata last modified” is the ingestion date, so right now GBIF only has observations up to April 13, from an ingestion done on April 17.
Remember that even if you uploaded an observation prior to the export generation date, it had to meet the qualifications on that date. So if it recently became RG, or you recently changed the license, it may have missed the cutoff.
If you want to see which of your observations have the badge/link back to GBIF (step five), you can use https://www.inaturalist.org/observations?outlink_source=GBIF&user_id=YOURUSERLOGIN
The original problem discussed at the start of this topic seems to be a real bug in the stats page – the page shows 11, but it provides a link which returns 232 results even though the stats have been regenerated recently.
(@Vincent_Mia_Edie_Verheyen I would recommend you make a new bug report, or I can make one on your behalf if you would prefer.)
There is separately another bug (also discussed above), which is that sometimes iNat fails partway through the badge creation process. It knows that the observation is in GBIF, but the badge isn’t there and a search with outlink_source=GBIF won’t find it. Re-indexing the observation (for example, by voting and unvoting a DQA) causes the badge to immediately appear. This bug was reported previously and discussion for that should ideally stay there.
but I note that it’s a separate issue/bug to the main issue being discussed in this thread.