Wolfgang8741 bot

GNIS edits

Hi,

I just noticed some issues with your bot, see Special:Diff/704781941 for example:

You should check for existing references. I had to remove two of the three you added there because the statements already had more complete references for the same source.

References should be more detailed, including retrieved (P813) and GNIS Feature ID (P590), where possible, see Help:Sources. If that seems like duplication, remember that references are independent of other statements on the item - there can be multiple GNIS IDs on an item and the IDs can be changed or removed (correctly or incorrectly).

Descriptions should start with a lowercase letter, unless the first word is a proper noun, see Help:Description.

Most users with bot accounts redirect the talk page for the bot account to the one for their main user account. If you want to do the same, feel free to move this section to your normal user talk page.

Also, you don't have a bot flag for this account. You shouldn't make any more edits until you do. There's still a question on Wikidata:Requests for permissions/Bot/Wolfgang8741 bot waiting for your response.

- Nikki (talk) 09:25, 5 September 2018 (UTC)

-- Hi @Nikki:, Thank you for the feedback. I didn't see the comment notification in my email, but I've addressed the comment. These were edits in my initial learning how to use Openrefine with WikiData. From my experience part of this is due to my learning Openrefine/WikiData import and partially due to the Openrefine interface lacking many checks for duplication of entries and being able to easily see current content overlap. My initial assumption was the import would be intellegent and merge overlapping content and not duplicate content only add a reference that agrees. If you noticed I stopped imports via Openrefine a while ago as I learned of deficiencies and need for an improved process (or Openrefine enhancement) to check the import process for these duplication and details. I agree the lack of import dates for these are less valuable and the defining of what the import/reference infrastructure needs to be addressed in the GNIS import, given the references have a timestamp in the page history we could apply the import date from that timestamp though I believe an additional field to include in the reference is what data export was used for GNIS to generate the imported value since the data is exported periodically and corrections are made. I stopped description imports since I didn't want to risk overwriting better descriptions, but was trying to provide some improved resolution and consistency where lakes had similar names.

I've found a handful of issues with GNIS already from the entity resolution process with WikiData items. When I started the import I was new to Openrefine and just learning WikiData import process. The now defined process is much clearer and until the community assessment for the import is complete and process to QA the import I'm holding off the data import while focusing on entity resolution for existing items via Mix-n-match. GNIS is somewhat less clean data to work with as the GNIS dataset has mixed types of content and needs to be split for import... so thank you again for pointing out these issues and the orientation process. Looking forward to collaborating on the GNIS data import configuration and process for a clean GNIS integration with WikiData. Glad to see someone monitoring my changes, most should be easily detectable and fixed! I manually reviewed many of the edits, must have missed this set. I could have used a better orientation earlier and the bot account was a way to clearly show this activity and gain feedback.

I'm keeping this talk separate, but it is actively monitored in my email.

The description standard for lowercase is noted, but a bot should be built to review and mod these. Really I think they should all be capitalized and full sentence descriptions, but that is for a discussion elsewhere.

Cheers! Wolfgang8741 (talk) 16:14, 5 September 2018 (UTC)