Jump to content

Wikidata:WikiProject LD4 Wikidata Affinity Group/Wikidata Working Hours/2021-May-24 Wikidata Working Hour

From Wikidata

May 24, 2021 Wikidata Working Hour

[edit]

Monday, May 24, 2021 at 11:00 am PT / 2:00 pm ET / 18:00 UTC / 8:00 pm CET

Recording

[edit]

This session was recorded, by request. View the recording.

Sign Up

[edit]

If you plan to attend, please sign up. You can sign your name by editing this page and typing *~~~~. If you have any problems signing up, email ld4-wikidata-coord@googlegroups.com with your username.

Logistics

[edit]

Join via Zoom: https://stanford.zoom.us/j/92800935859?pwd=TGVKbDdxMGRSQ09uYkJsOXY3ZWltUT09
Password: 693496
Please note: this session will be recorded, by request.
Create a Wikimedia account if you don't already have one

Metrics

[edit]

Login to the Event Dashboard with your Wikimedia account to keep track of your edits today

In Preparation for the Session

[edit]

Please consider going through these set up steps in advance of the session. We will do our best to help with technical issues, but we hope everyone will be able to take advantage of the whole hour. This session will focus on the Wikidata side of things and not on programming, command line, etc. As is the case with many "follow-along" workshops, the biggest hazard is running into technical issues at the start and not being able to "keep up" because of getting stuck with installation issues, getting lost, etc. Therefore, if you don't already have Python 3 installed on your computer, don't know how to get to the command line, don't know where your home directory is, etc., you can do some up-front legwork to avoid these hazards.

1. Accessing the command line. To get to the command line, you need to open a console program that is appropriate for your operating system. For Macs and Linux that is typically the Terminal application. On Windows, it is typically the Command Prompt application. (Some Windows users know how to launch the Linux shell -- if you know how to do that, it's fine.) If you need more information about accessing the command line, see this page for Windows or this page for Mac.

2. Checking whether you already have Python 3. It is possible that your computer already has Python 3 installed on it -- for example if you've installed Anaconda for other purposes. You should be aware that many Macs have Python 2 pre-installed as part of the operating system. Python 2 is deprecated and will NOT work for these exercises. Starting with the Big Sur operating system, Python 3 is included, so the Python version you have probably will depend on what OS you are using.

To find out whether Python 3 is installed on your computer, open your console (see #1 above) and enter

python

If the console responds with something like Python 3.7.2... or some other number starting with "3", then you are good to go (usually the case for Windows users). If it says something like Python 2.7.16 or some other number starting with "2" (usually the case for Mac users), then try the next thing. If you get an error message, also try the next thing.

If you didn't get a message like Python 3.7.2, then try entering

python3

If the console responds with something like Python 3.7.2... or some other number starting with "3", then you are good to go, but you need to remember that in the future, any time the instructions tell you type "python ...", you need to instead type "python3 ..." (usually the case for Mac users who haven't installed Anaconda). If you get an error message after trying both of these things, then you don't have Python 3 and need to install it.

If you got into either Python 2 or Python 3, you can get out of it by holding down on the Ctrl key and pressing the Z key (or just close the console window).

3. Installing Python 3 (if you don't already have it). There are instructions for installing Python 3 on both Mac and Windows on this page. Note to Windows users: one of the most common problems is not having Python 3 added to your system path! Note carefully in step 4 that there is a checkbox during the installation to do this. If you forget to check this box, it is possible (but difficult) to fix and you will probably need to ask for help from an advanced user.

To enable secure communications through Python, Python will need a security certificate. On Macs, the last step of the installation may include a message about downloading and installing SSL root certificates. If so, run the "Install Certificates" script as instructed in the final window.

Once you have installed Python 3, you can go back to the last step and verify that you can get Python 3 to start up in your console program.

4. Installing the requests package. I believe that the scripts we will be using need only one module that isn't in the Standard Library for Python. That is the package called requests. The requests package is used to communicate between your computer and servers somewhere else using HTTP, the communications language of the Internet. If you are not an Anaconda user, to install the requests package, open your terminal program and type the following (substituting "pip3" instead of "pip" if you have to type "python3" instead of "python" on your computer):

pip install requests

5. Figuring out where your downloaded files are. If you don't typically navigate around your computer using the command line, it is possible to get lost. I recommend that you create a folder that is a subfolder of your Documents folder in which to put the files that we will be using (for example a folder called "vanderbot" or something else that is simple and doesn't have spaces in its name). Most people can easily get to such a folder, although Windows is particularly bad about making people confused about where files are. If you want to run a test ahead of time, try creating a subfolder of your Documents folder, download a file into it, then try the following commands in the console:

cd Documents

then

ls for Mac, or dir for Windows

You should see the directory you created. Now change to the new folder and look for the file you downloaded by entering these commands:

cd vanderbot (or whatever you called the folder)

then

ls for Mac, or dir for Windows

You should see the file you downloaded in the listing. Sometimes in Windows weird things happen with different user folders, so if you can't find the file you downloaded, ask a more experienced user for help.

6. Using a text editor. At several points in the session, we will need to edit plain text files. Those are files that don't have all of the extra "invisible" information that is saved in word processing documents. Both Macs and Windows computers have built-in text editors that you can use: TextEdit on Macs and Notepad on Windows. If you have installed a code editor like Atom or Visual Studio Code on your computer, you can use that instead, but that's overkill. If you don't know about text editors or don't know how to find one on your computer, there are some videos on the topic you can watch here. NOTE: If this is the first time you have used TextEdit on a Mac to edit plain text, make sure that you have set it to default to plain text rather than rich text. See these instructions for more details.

For more help... If you can make it through these steps, you will be ready to go for the session. If you run into problems, you can email me for help at steve.baskauf@vanderbilt.edu .

Resources

[edit]

Video tutorial page

First DIY blog post

bot password page

Wikidata test instance (playground)

Test items in the "real" Wikidata:

VanderBot Python script (for downloading)

Online schema-builder

Script to convert simplified configuration file into a schema

practice configuration file for sandbox pages

practice configuration file for adding real faculty items

script for downloading existing data

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:WikiProject_LD4_Wikidata_Affinity_Group/Wikidata_Working_Hours/2021-May-24_Wikidata_Working_Hour&oldid=2031355716"