Mae Jemison's Wikipedia entry

@zkamvar
We need to update style for this lesson so that jump lists (anchors for different sections) becomes automatically available for different levels of headings.

Change the example from Richard Feynmann to an example of showing all books from one author

• maybe choose another author (e.g. Albert Einstein)

Can we learn/use anything form this excellent course by @fuzheado (digged out by @libcce)?

https://www.oclc.org/content/dam/research/events/2018/oclcresearch-lih-fernandez-introduction-to-wikidata-wip-2018.pdf

E.g search for books or something. Warning - searching for all scholarly articles will take long and lead to a time-out. Suggestion - search for articles of a certain authors.

This has IMO low priority but it would be great if we could automate the screenshot generation e.g. using Selenium. It would make it more reproducible and speed up things on the long run.

While looking at adapting the current example (Feynman and one of his books) to use Mae Jemison and one her books, I'm wondering whether it might make more sense to add detailed steps for describing the first item (Mae Jemison) rather than the second one (her book), for two reasons:

1. It seems weird to not add an instance and at least one profession based on Jemison's Wikipedia entry, which would also be easy to add as a reference. (Her memoir doesn't have a Wikipedia entry and describing it, with references, would require the learner to look for external sources, which doesn't seem to be the emphasis of this exercise.)
2. Describing the book would require delving into more complex modeling (is it an instance of "book" or "written work" or "version, edition, or translation"?
   See https://www.wikidata.org/wiki/Wikidata:WikiProject_Books

look in
https://github.com/LibraryCarpentry/lc-wikidata/blob/gh-pages/_episodes/02-linked_data.md

some key ideas:

How far do we need to go with defining concepts.
like different ways of orginising/structuring data
differenent types of data containers/bases
usages and best practices for each
showing differences and alternatives quering languages.

The episode 01 intro includes this sentence: "The data can be queried with SPARQL which will be covered later." I suggest we briefly explain what SPARQL is, even if it just to call it the SPARQL querying language, so that participants who have never heard of SPARQL have at least some context at this point - is it a tool? a script?, etc. I know it gets explained in depth later, but I could see this intimidating people who have never heard of it - because it's not explained even a little (outside of the verb queried), there could be an assumption that people should know what SPARQL is already.

participants need to be registrated in wikidata for four days to be able to edit wikidata items.
Add information to instrutor notes

publication: https://zenodo.org/record/7683713
NFDI Sites with Python: https://git.rwth-aachen.de/matthias.fingerhuth/NFDI-Wikidata/-/blob/main/NFDI_Wikidata_map_by_subject_areas.ipynb

Might be more useful for Python lesson

Currently we have used several pads on hackMD. The content of them should be added to the repo. Maybe also generate a template for the pad for future meetings.

• add at the end of episode 4

The Contributing Guide, CONTRIBUTING.md, contains two links with URLs that should be updated:

1. the How to Contribute to an Open Source Project on GitHub link leads to a 404 and should be updated to link to https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github
2. the [repo] link reference currently points to a placeholder URL (https://example.com/FIXME) and should be updated to point to the source repository for the lesson (i.e. this GitHub repository).

The Contributing Guide is one of the files that is unique to each repository - to allow for individual lesson projects to define their own guidance for contributors - so unfortunately this is not an issue that can be fixed centrally e.g. by updating the template files in the lesson infrastructure. Instead the file must be updated in the individual lesson repositories themselves.

Results from @Tillsa, @elhossary and me:

https://github.com/zbmed/lc-wikidata/blob/gh-pages/Topic_list_brainstorming.md

Any further suggestions?

Add the following article to the references
Bianchini, C., & Sardo, L. (2022). Wikidata: a new perspective towards universal bibliographic control. JLIS.It, 13(1), 291–311. https://doi.org/10.4403/jlis.it-12725 / https://www.jlis.it/index.php/jlis/article/view/439

In the lesson 01-introduction, section 1.2 "Play games to open" is lacking games to play. So far the only "game" is opening a random item page. Ideas for other Wikidata related games / ice-breakers are needed.

I recently completed my Library Carpentries training course with a view to helping out and contributing to Wiki-based lessons specifically. Is this one still in development? I would be really happy to help get it over the finish line. I apologise if this lands in the wrong area.

In terms of suggestions, I wonder if 1.1 could utilise just one example plus visual: at the moment we read about one (the Library) but see the described terms on another (Douglas Adams). In 1.2, we ask for participants to look up their home city: maybe country would be better, as this will cover a wider range of possibilities.

These are small things and by no means urgent! I'd love to carry on the conversation around this module, I'm [email protected], currently Wikimedian in Residence at the British Library.

One exercise of the LC is supposed to contain a task where learners create a new item on Wikidata and add a new statement to an already existing item. The issue that we face right now is which kind of items we should chose. The items/entities need to meet some criteria:

• have something to do with libraries
• don't exist yet
• have enough relevance, so they won't be deleted by other people after the lesson
• can be updated automatically (by a bot)

Alternatively we can use the Wikidata Sandbox. But creating items in the "real world" of Wikidata is preferable. If you have any ideas please share them :)

Episode 6 contains "Norms" - which norms exist already and are relevant for novices to know?

The Linked Open Data Cloud is a good visualization of the state of LOD and could help to understand the underlying purpose of a knowledge graph. It could fit in figure 2. It is CC-BY licensed. One issue is that it is updated regularly.

Hi @maneesha can you create a lesson team for Wikidata and invite:

• Till Sauerwein
• Muhammad Elhossary
• Konrad Förstner

Replace the word "understand" in the learning objectives of episode 01 with something more specific. Blooms Taxonomy can be used to get some ideas:
https://cft.vanderbilt.edu/guides-sub-pages/blooms-taxonomy/

Short version: are you are willing to volunteer your lesson for early transition to The Carpentries Workbench
infrastructure?

Longer version below:

As I hope you are already aware, @zkamvar and the rest of the Curriculum Team are preparing to roll out the new lesson infrastructure, The Carpentries Workbench, across all of The Carpentries official lessons in early May 2023. This means that all Data Carpentry, Library Carpentry, and Software Carpentry lesson repositories will be modified to adopt the new infrastructure at the end of this month.

As you might imagine, coordinating a rollout like this involves a large amount of time and effort, and one thing that will really help us to keep to the schedule and avoid disruption for the community is to be able to prepare some lessons for
transition before the 1st May deadline.

With this in mind, I invite you to volunteer to schedule an early transition for theis lesson repository. If you expect to have time to adopt the Workbench version of the lesson repository in the next couple of weeks, please reply to let me know. As lesson Maintainers, these are the things you will need to be prepared to do for the transition:

1. Be prepared to quickly merge pull requests from Zhian. These pull requests will help update the lesson and aid the transition process.
2. Close any outstanding pull requests. Your repository currently has very few or zero open PRs, but we cannot rule out the possibility that someone will open more in the time between now and when the transition takes place. Open PRs will be invalidated when the transition takes place.
3. Preview the lesson (in the https://github.com/fishtree-attempt organisation) when it is available. Zhian will open an issue in your repository, tagging you when the preview is available. You should reply on that issue if you notice any problems with the Workbench version of the lesson site and repository in the preview.
4. Just before the transition happens, the repository will be temporarily set as read-only and an issue will be opened (see an example from the Maintainer Onboarding curriculum: carpentries/maintainer-onboarding#69)
5. After the transition, delete and recreate any forks and local clones you have of the repository and then confirm that you have done so (you will be given specific instructions in an issue).

If you are willing and able to help us ensure a smooth rollout of the Workbench, please reply to let me know that you are happy to volunteer your lesson for early transition. If there is a specific date you would like the transition to take place (or that we should avoid), please also mention that.

e.g.

• wb-cli (for bulk editing)
• author disambiguator

The books as an example are not that easy in case of data models and good pracitce.
Suggestion is to use new research articles in the real wikidata instance instead.

• add research article example in episode 3 as an alternative option
• mention the two different options in the instructor notes

In the Wikidata sprint during CarpentryCon @ Home, @RabeaMue mentioned there are challenges adding images under episode 2

add motivation and "why" to use wikidata as one topic.
Especially why to use an librarian

• maybe also through real case (e.g. scholia)

We currently have different writings for "Wikidata":

1. Wikidata (as it is also written in Wikidata, see Q2013)
2. WikiData
3. wikidata

Can we be more consistent and use always the first one? I.e. use an upper-case "W" but everything else lower-case. The links to Wikidata should stay all-lowercase as usual.

Might it be useful to briefly state that Wikidata is not Dbpedia? I have, anecdotally, seen this cause confusion among librarians. Making distinctions between the goals of the two projects (and where they overlap) might also help participants to understand the relationship between Wikidata and Wikipedia. (Apologies if this idea has already been discussed.)

The initial "Wikidata" seems to be too unspecific. Should it be extended to "Wikidata for librarians" or something else?