Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Propuesta de lección: Promoviendo la ciencia abierta con Wikidata: visibilidad y apertura de los Portales de Revistas Académicas #589

Open
jenniferisasi opened this issue Sep 22, 2023 · 53 comments
Open

Propuesta de lección: Promoviendo la ciencia abierta con Wikidata: visibilidad y apertura de los Portales de Revistas Académicas #589

jenniferisasi opened this issue Sep 22, 2023 · 53 comments
Assignees
@jenniferisasi
Labels
6. Sustainability + Accessibility Español Original

Comments

@jenniferisasi
Copy link
Contributor

jenniferisasi commented Sep 22, 2023 •
edited
Loading

The Programming historian en español ha recibido una propuesta de lección con el título provisional "Promoviendo la ciencia abierta con Wikidata: visibilidad y apertura de los Portales de Revistas Académicas" por Cláudia De Souza @ClaudiaDeSouza y @Dmwilsonfraites Dinah Wilson Fraites. Los objetivos de la lección son:

  • Mejorar el entendimiento sobre Wikidata y la estructuración de sus registros
  • Contribuir a la búsqueda, recuperación, conservación e interoperabilidad de los datos abiertos enlazados

A fin de promover una publicación a tiempo, se ha acordado que la lección se entregará hacia mediados de diciembre de 2023 febrero de 2024. La autora contactará con antelación con la editora si no puede cumplir con la fecha de entrega y necesita una ampliación.

Si la lección no es entregada en la fecha acordada, la editora intentará contactar con el autor o autores de la lección. Si no recibe noticias, el ticket se cerrará. Éste podrá abrirse en el futuro a petición del autor o autores.

El principal contacto para esta lección es, por ahora, @jenniferisasi. Si se produce algún problema, el autor puede contactar con nuestra ’ombudsperson' (Silvia Gutiérrez de la Torre - http://programminghistorian.org/es/equipo-de-proyecto).
@jenniferisasi jenniferisasi self-assigned this Sep 22, 2023
@jenniferisasi jenniferisasi moved this to 0 Proposal in Active Lessons Sep 22, 2023
@jenniferisasi
Copy link
Contributor Author

La autora me ha contactado sobre su progreso. Va a incorporar a una co-autora para ampliar una sección de la lección y nos remitirán el primer borrador pronto.

@jenniferisasi
Copy link
Contributor Author

Las autoras me han enviado su primer borrador (en formato Word), que leeré en los próximos días y, de ahí, añadiré a las co-autoras a este ticket para dejar mis comentarios.

@anisa-hawes
Copy link
Contributor

anisa-hawes commented May 27, 2024 •
edited
Loading

Hola @jenniferisasi. If you'd like to share this draft with us, we'd be very happy to convert it into Markdown and generate a preview.

@jenniferisasi jenniferisasi moved this from 0 Proposal to 1 Submission in Active Lessons May 30, 2024
@jenniferisasi
Copy link
Contributor Author

Hola @jenniferisasi. If you'd like to share this draft with us, we'd be very happy to convert it into Markdown and generate a preview.

Thank you @anisa-hawes and @charlottejmc! I will forward you the authors' email with the Word doc. I started reading it (very much enjoying it) but realized it would be easier to do this first pass already with the markdown paragraph numbers :)

Let me know if I can assist in anything in the meantime.

@anisa-hawes
Copy link
Contributor

Hello @jenniferisasi. Thank you for sharing this. We'll make a start setting this up.

--

Hello Cláudia. Could you share the image files with us as .png or .jpeg files? Please email them to Charlotte (publishing.assistant[@]programminghistorian.org) so we can generate a preview of your draft 🙂

Thank you, Anisa

@charlottejmc
Copy link
Collaborator

charlottejmc commented May 31, 2024 •
edited
Loading

Hola @jenniferisasi, @ClaudiaDeSouza y @Dmwilsonfraites,

Puedes encontrar los archivos aquí:

Puedes revisar la vista previa de la lección aquí:

I would like to bring your attention to a couple small adjustments I made while processing this lesson:

  • I edited the lesson structure very slightly, so that it reads this way:
## Introducción
### Objectivos de la lección
### Prerrequisitos
## ¿Qué es Wikidata?
## La estructura de Wikidata
## Paso a paso crear una cuenta y un elemento en Wikidata
## Describiendo datos de revistas en Wikidata
## Describiendo datos de personas en Wikidata
## Herramientas sugeridas para la descripción de elementos en Wikidata
## Referencias

I added the title Objectivos de la lección and brought that paragraph down below the conceptual discussion of metadata etc. in the Introducción, followed by the very short Prerrequisitos. We can still edit the structure to turn some headings into subheadings, if necessary.

  • I chose the lesson slug estructurar-metadatos-academicos-con-wikidata because it seemed to describe the objective of the lesson, and it starts with an action verb, which aligns with our house style. This currently doesn't exactly 'fit' the provisional lesson title, but I believe the title may be adjusted in future revisions. We can also edit the slug as desired.

  • I will upload the images when I receive the files, and edit the markdown to link them in. Cláudia, the syntax which we use to embed figures within our lessons includes a 'figure caption' (which you've provided already), and an 'alt-text'. This descriptive element enables screen readers to read the information conveyed in the images for people with visual impairments, different learning abilities, or who cannot otherwise view them, for example due to a slow internet connection. It's important to say that alt-text should go further than repeating the figure captions.

We have found Amy Cesal's guide to Writing Alt Text for Data Visualization useful. This guide advises that alt-text for graphs and data visualisations should consist of the following:

alt="[Chart type] of [data type] where [reason for including chart]"

What Amy Cesal's guide achieves is prompting an author to reflect on their reasons for including the graph or visualisation. What idea does this support? What can a reader learn or understand from this visual?

The Graphs section of Diagram Center's guidance is also useful. Some key points (relevant to all graph types) we can take away from it are:

  • Briefly describe the graph and give a summary if one is immediately apparent
  • Provide any titles and axis labels
  • It is not necessary to describe the visual attributes of the graph (colour, shading, line-style etc.) unless there is an explicit need
  • Often, data shown in a graph can be converted into accessible tables

For general images, Harvard's guidance notes some useful ideas. A key point is to keep descriptions simple, and adapt them to the context and purpose for which the image is being included.

Would you feel comfortable making a first draft of the alt-text for each of the figures? This is certainly a bit time-consuming, but we believe it is very worthwhile in terms of making your lesson accessible to the broadest possible audience. We would be very grateful for your support with this.

Thank you,

Charlotte ✨

@jenniferisasi jenniferisasi moved this from 1 Submission to 2 Initial Edit in Active Lessons May 31, 2024
@anisa-hawes
Copy link
Contributor

anisa-hawes commented May 31, 2024 •
edited by charlottejmc
Loading

Hola @ClaudiaDeSouza y @Dmwilsonfraites,

What's happening now?

Your lesson has been moved to the next phase of our workflow which is Phase 2: Initial Edit.

In this phase, your editor Jennifer @jenniferisasi will read your lesson, and provide some initial feedback. Jennifer will post feedback and suggestions as a comment in this issue, so that you can revise your draft in the following phase (Phase 3: Revision 1).

%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
              'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
              'cScale1': '#535d7f', 'cScaleLabel1': '#ffffff',
              'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
       } } }%%
timeline
Section Phase 1 <br> Submission
Who worked on this? : Publishing Assistant (@charlottejmc) 
All  Phase 1 tasks completed? : Awaiting figure images
Section Phase 2 <br> Initial Edit
Who's working on this? : Editor (@jenniferisasi)  
Expected completion date? : June 30
Section Phase 3 <br> Revision 1
Who's responsible? : Authors (Cláudia + Dinah) 
Expected timeframe? : ~30 days after feedback is received
Loading

Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment.

@charlottejmc
Copy link
Collaborator

charlottejmc commented Jun 7, 2024 •
edited
Loading

Hello @ClaudiaDeSouza y @Dmwilsonfraites,

Thank you very much for sending over the image files. I've uploaded them to the lesson's image folder, and you can see how they look in the lesson preview.

Can I just take this opportunity to point you back to my initial comment above? There are still a couple outstanding points – including alt-text for the images.

Thank you ✨

@Dmwilsonfraites
Copy link
Collaborator

Dmwilsonfraites commented Jun 7, 2024 via email

@charlottejmc
Copy link
Collaborator

Hi @Dmwilsonfraites,

Thanks very much for your quick response!

Yes, 'Visual description of figure image' is exactly where we would need the alt-text. You're also right about how to edit the file – the only issue is I'm not sure you've been given write access to be able to make direct edits. My colleague @anisa-hawes will look into this for you!

In the meantime, you could simply write them in a comment below (e.g Figura 1 - [alt-text here]), and I can take care of adding them in myself.

@anisa-hawes
Copy link
Contributor

anisa-hawes commented Jun 7, 2024 •
edited
Loading

Hello Dinah @Dmwilsonfraites,

I've sent you and Claudia @ClaudiaDeSouza invitations to join us here on GitHub as outside collaborators. This will give you both the Write access you'll need to edit your file directly here: /es/borradores/originales/estructurar-metadatos-academicos-con-wikidata.md.

Please let us know if you encounter any practical difficulties. Charlotte and I are here to help ☺️

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Jun 7, 2024 via email

@ClaudiaDeSouza
Copy link
Collaborator

Thank you very much!
What deadline do we have for for completing this?
Next week I'll be out of the office, I could start on Monday, June 17th.
Please let me know if it's possible.

@anisa-hawes
Copy link
Contributor

Dear @ClaudiaDeSouza.

There's no immediate rush to complete the alt-text. We can slot that in whenever we receive it. Jennifer is reading the lesson already, and will return with initial feedback for you by ~30 June.

Thank you.

@jenniferisasi
Copy link
Contributor Author

Estimadas autoras @ClaudiaDeSouza y @Dmwilsonfraites, felicidades por una lección tan informativa a la vez que clara en sus instrucciones. El orden de estas así como el estilo y los ejemplos son excelentes y en general no necesitan revisión. Como indico abajo, lo único que recomiendo para mejorar este trabajo es una sección de conclusión más fuerte. El resto de mis sugerencias son mínimas y más que nada para facilitar la lectura; puede que los revisores pidan más cambios pero como edición primera no va a ser necesario mucho trabajo.

Los siguientes números corresponden al párrafo que pueden ver en la previsualización:

  • 2: "por lo tanto, sería algo como 'datos sobre los datos'. Precisamente, los metadatos son 'datos que hablan... "
  • 2: "así como facilitando la interoperabilidad" - facilitan
  • 2: "disponible en línea, ya que son esenciales..." - y son
  • 3: "(lo que en inglés serían los Open Data)" - (Open Data en inglés)
  • 5: "de la investigación. Abordaremos las revistas..." - de la investigación. Como caso de estudio abordaremos..."
  • 13: añadir enlace a referencia de "web semántica"
  • 16-27: sugiero hacer submenús con cada "elemento" para que los lectores puedan referirse a ellos con un vistazo rápido
  • 30: "En este caso (caso), debes de dirigirte" - la palabra caso está duplicada, creo
  • 37: indicar explícitamente si se trata de valores fijos, es decir, de un vocabulario controlado al que tenemos que ceñirnos los usuarios o si es de entrada libre (para que los lectores no tengan que esperar a ir a esa fase de añadir datos para corroborarlo)
  • 70: Necesitamos un párrafo de cierre de la lección, al igual que si de un artículo tradicional se tratara. Un resumen de lo aprendido, las posibles aplicaciones y la sugerencia a seguir aprendiendo con la lección mencionada bastarían.

Quedo al pendiente para aclarar cualquier duda que estos comentarios pudieran ocasionar y dar ya comienzo a la tercera fase de nuestro workflow. ¡Gracias!

@anisa-hawes anisa-hawes moved this from 2 Initial Edit to 3 Revision 1 in Active Lessons Jun 21, 2024
@charlottejmc
Copy link
Collaborator

Hola @ClaudiaDeSouza,

Yes, @jenniferisasi will first provide a summary of both reviews, so that you can have a clear sense of the revisions to work through in Phase 5.

Gracias por esperar ✨

@jenniferisasi
Copy link
Contributor Author

¡Muchas gracias por tan atenta revisión @pedronilsson! Sí, haré un resumen de todo lo propuesto para facilitar el proceso.

@ClaudiaDeSouza deme unos días para realizar el resumen; recién viajé estos días de España a EEUU y tengo otro viaje programado para el viernes y sábado.

Vamos muy bien :) y feliz de ver esta lección entrar en las fases finales.

@jenniferisasi
Copy link
Contributor Author

jenniferisasi commented Oct 16, 2024 •
edited by anisa-hawes
Loading

Estimadas @ClaudiaDeSouza y @Dmwilsonfraites, gracias en primer lugar por su paciencia. Como vieron, han recibido muy buenas revisiones por parte de @semanticnoodles y de @pedronilsson, con pequeñas puntualizaciones para mejorar la fluidez del texto y complementar información que puede facilitar la comprensión más completa de la lección.

Aquí les dejo el resumen de lo que se indica más o menos en ambas revisiones, además de los puntos concretos que indica cada una (y que todavía no han editado):

  • A lo largo de la lección, consolidad el uso del tú al lector y evitar la estructura impersonal como en P 45: "se ha incluido" vs "hemos incluido"
  • Mejorar la introducción con una formulación más directa sobre la dirección y audiencia de la lección
  • A la vez, aclarar los objetivos tras la introducción.
  • De ahí, crear una subvención dedicada a Definiciones básicas con las definiciones del inicio.
  • En esa sección, incluir una mención a Wikipedia por ser el proyecto más conocido
  • Aclarar que LOD son las siglas en inglés y utilizar DAE o Datos Abiertos Enlazados
  • Figuras / Los textos de las figuras 11 y 12 son difíciles de leer; si es posible, aumente la resolución de la captura de pantalla.
  • p 17: "No es necesario... ...específicos" me parece un poco confuso. Creo que la frase anterior ya explicaba perfectamente el concepto de identificador único; el último fragmento se podría evitar, o reescribir para aclarar si un identificador universal y un identificador único son conceptos diferentes o no.
  • P 30 Quizá vale la pena añadir que también se puede utilizar la cuenta existente de Wikipedia (además de la de Wikimedia)
    Y finalmente los typos identificados por Pedro:
    Typos:
  • P 5 "explican" en lugar de "explica"
  • P 17 cambiar la coma entre "número" y "por ejemplo" por un punto y seguido.
  • P 23 "al español" en lugar de "en español"
  • P 27 "coordenadas geográficas o archivos multimedia, entre otros."
  • P 31 "crear un nuevo ítem" debería ser "crear un elemento nuevo" para coincidir con figura 8
  • P 33 "debemos de seguir" eliminar "de"
  • P 37 "describir a París" eliminar "a"
  • P 40 Quizás valdría la pena formatear el nombre de la revista "Acceso:.." a cursiva?
  • P 41 Añadir una coma después de "destacar que",
  • P 47 Ocurre algo con el formato de "Digital Object identifier" quizás falta un espacio antes de la barra baja.
  • P 48 igual que P 40, Acceso en cursiva?
  • P 52 "en tanto" sustituir por "ya que"
  • P 72 "sobre este tema" a "sobre el tema"

Como siempre, quedo al pendiente de aclarar cualquier duda o problema que pueda surgir y, por supuesto, cualquier comentario que quieran realizar o aclarar sobre las revisiones recibidas.

Mil gracias de nuevo a @semanticnoodles y @pedronilsson por sus tan atentas revisiones.

@anisa-hawes anisa-hawes moved this from 4 Open Peer Review to 5 Revision 2 in Active Lessons Oct 16, 2024
@anisa-hawes
Copy link
Contributor

Hola Cláudia @ClaudiaDeSouza y Dinah @Dmwilsonfraites

What's happening now?

Your lesson has been moved to the next phase of our workflow which is Phase 5: Revision 2.

This phase is an opportunity for you to revise your draft in response to the peer reviewers' feedback.

Jennifer @jenniferisasi has summarised their suggestions, but feel free to ask questions if you are unsure.

Please make revisions via direct commits to your file: /es/borradores/originales/estructurar-metadatos-academicos-con-wikidata.md. @charlottejmc and I are here to help if you encounter any difficulties.

When you and Jennifer are happy with the revised draft, Jenn will re-read (with her Managing Editor 'hat' on!) before we move forward to Phase 6: Sustainability + Accessibility.

%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
              'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
              'cScale1': '#535d7f', 'cScaleLabel1': '#ffffff',
              'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
       } } }%%
timeline
Section Phase 4 <br> Open Peer Review
Who worked on this? : Reviewers (@semanticnoodles + @pedronilsson)
All  Phase 4 tasks completed? : Yes
Section Phase 5 <br> Revision 2
Who's working on this? : Authors (@ClaudiaDeSouza + @Dmwilsonfraites)
Expected completion date? : Nov 17
Section Phase 6 <br> Sustainability + Accessibility
Who's responsible? : Publishing Team
Expected timeframe? : 7~21 days
Loading

Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment.

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Nov 7, 2024 via email •
edited by anisa-hawes
Loading

@jenniferisasi
Copy link
Contributor Author

¡Estimadas autoras @ClaudiaDeSouza y @Dmwilsonfraites!

Gracias por editar su lección con los comentarios de los revisores tan prontamente y disculpen mi tardanza. Quería releer de nuevo bien las secciones para asegurarme de dar una respuesta adecuada a su pregunta. Tienen razón en que incluir un glosario sería redundante tal y como están ahora mismo la introducción - que ya tiene varias definiciones- y la sección "¿Qué es Wikidata?". Así que podemos dar eso por solucionado. ¿Qué les parece?

Si están de acuerdo continúo mi lectura para dar después comienzo a la Fase 6. ¡Gracias!

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Nov 20, 2024 via email

@jenniferisasi
Copy link
Contributor Author

I have now read the lesson again and I declare it ready to move it to Phase 6, since the authors have done a great job in incorporating suggestions.

@anisa-hawes and @charlottejmc this is now in your hands :) Thanks!

@anisa-hawes
Copy link
Contributor

Hola Cláudia @ClaudiaDeSouza y Dinah @Dmwilsonfraites,

What's happening now?

Your lesson has been moved to the next phase of our workflow which is Phase 6: Sustainability + Accessibility.

In this phase, our publishing team will coordinate a series of tasks including: copyediting, typesetting, generating archival links, collating copyright agreements, and reviewing essential metadata.

Please note that you won't have direct access to make further edits to your files during Phase 6. You will have an opportunity review and discuss suggested copyedits with your editor @jenniferisasi. Thank you for your understanding.

When our Sustainability + Accessibility actions are complete, the Managing Editor will read the lesson/translation through one final time ahead of publication.

%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
             'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
             'cScale1': '#535d7f', 'cScaleLabel1': '#ffffff',
             'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
      } } }%%
timeline
Section Phase 5 <br> Revision 2
Who worked on this? : Authors (@ClaudiaDeSouza + @Dmwilsonfraites)
All  Phase 5 tasks completed? : Yes
Section Phase 6 <br> Sustainability + Accessibility
Who's working on this? : Publishing Team
Expected completion date? : ~21 days
Section Phase 7 <br> Publication
Who's responsible? : Managing Editor @jenniferisasi
Expected timeframe? : ~10 days
Loading

Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment.

@anisa-hawes anisa-hawes moved this from 5 Revision 2 to 6 Sustainability + Accessibility in Active Lessons Dec 4, 2024
@anisa-hawes
Copy link
Contributor

anisa-hawes commented Dec 11, 2024 •
edited
Loading

Hola Cláudia @ClaudiaDeSouza, Dinah @Dmwilsonfraites y @jenniferisasi,

I've prepared a PR with the copyeditor's suggested changes for your review.

There, you'll be able to review the 'rich-diff' to see their suggested edits in detail.

When you're all happy, we can merge in the PR and move forwards with our next steps towards publication.

¡Gracias!

@anisa-hawes
Copy link
Contributor

Thank you for reviewing the copyedits, @ClaudiaDeSouza and @Dmwilsonfraites!

Next, Charlotte @charlottejmc will carry out a series of Sustainability + Accessibility tasks including: typesetting, generating archival links, collating copyright agreements, and reviewing essential metadata.

When these tasks and checks are complete, the Managing Editor @jenniferisasi will read your lesson through one final time ahead of publication ✨

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Dec 11, 2024 via email

@charlottejmc
Copy link
Collaborator

charlottejmc commented Dec 17, 2024 •
edited
Loading

Hello @jenniferisasi,

This lesson's sustainability + accessibility checks are in progress.

  • Preview:

http://programminghistorian.github.io/ph-submissions/es/borradores/originales/estructurar-metadatos-academicos-con-wikidata

Publisher's sustainability + accessibility actions:

  • Copyediting
  • Typesetting
  • Addition of Perma.cc links
  • Check/resize images
  • Check/adjust image filenames
  • Receipt of author(s) copyright agreement – Hola @ClaudiaDeSouza and @Dmwilsonfraites, nuestro formulario de declaración es para reconocer sus derechos de autor y concedernos permiso para publicar esta lección. Por favor, ¿podría descargar y rellenar este formulario? Envíelo por e-mail a (publishing.assistant [@] programminghistorian.org). Muchas gracias. (We only need one of you to provide this agreement.)
  • Request DOI
  • Remove outside contributors from ph-submissions

Authorial / editorial input to YAML:

  • Define difficulty:, based on the criteria set out here
  • Define the research activity: this lesson supports (acquiring, transforming, analysing, presenting, or sustaining) Choose one
  • Define the lesson's topics: (api, python, data-management, data-manipulation, distant-reading, get-ready, lod ["Linked Open Data"], mapping, network-analysis, web-scraping, website ["Digital Publishing"], r, machine-learning, creative-coding, web-archiving or data-visualization) Choose one or more. Let us know if you'd like us to add a new topic. Topics are defined in /_data/topics.yml.
  • Provide alt-text for all figures
  • Provide a short abstract: for the lesson (1-2 sentences)
  • Agree an avatar (thumbnail image) to accompany the lesson

The image must be:

  • Provide avatar_alt: (visual description of that thumbnail image)
  • Provide author(s) bio for ph_authors.yml using this template:
- name: Forename Surname
  orcid: 0000-0000-0000-0000
  team: false
  bio:
    es: |
      Forename Surname es profesor adjunto en el Departamento de Asignaturas de la Universidad de Ciudad.

Files we are preparing for transfer to Jekyll:

Promotion:

  • Prepare announcement post (using template)
  • Prepare evergreen posts – @jenniferisasi, could you please provide x2 posts for future promotion via our social media channels? You can add these directly to the ph-evergreens-bluesky spreadsheet that has been shared with you, or email them to me at publishing.assistant[@]programminghistorian.org.

Publisher's post-publication tasks:

  • Add lesson slug to the Annual Count of Published Lessons
  • Update the ph_data folder in the ph-contributors repository

Additional notes:

Hola @ClaudiaDeSouza and @Dmwilsonfraites, there are a few additonnal things I noticed when typesetting the lesson – I hope you can help me out!

  • Could you please provide the Spanish translation for the words "bots" and "library science journal", to add in parenthesis after the English terms?
  • Could you please provide the full citation for "Obregón Sierra, 2022"? I believe it was missing from the references.

Thank you very much for your patience and your energy.

@charlottejmc
Copy link
Collaborator

charlottejmc commented Dec 17, 2024 •
edited
Loading

Hello again @ClaudiaDeSouza and @Dmwilsonfraites,

I had a little look around the British Library for a potential image to use as a lesson thumbnail. I quite like the idea of a botanical illustration showing a branch and all the different related parts of the plant, like:

If you like this idea, you could browse through this album to find a favourite.

Another simple idea is an illustrated letter W (for Wikidata) which again, could come in different variations.

What do you think? Please feel free to suggest something completely different, as long as it matches our requirements described above.

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Dec 17, 2024 via email •
edited by charlottejmc
Loading

@Dmwilsonfraites
Copy link
Collaborator

Dmwilsonfraites commented Dec 17, 2024 via email

@charlottejmc
Copy link
Collaborator

charlottejmc commented Dec 18, 2024 •
edited
Loading

Dear @ClaudiaDeSouza,

Thank you very much everything you have provided above.

A few things:

  • Unfortunately, we cannot received attached files in GitHub comments. Could you kindly send the copyright form directly to my email, publishing.assistant [@] programminghistorian.org? Gracias!
  • We don't currently have the topic 'Metadata', but we can look into adding it to our list.
  • Thanks for your feedback about the Letter W! If @Dmwilsonfraites also likes the idea, perhaps you can find a favourite style in this album? Or perhaps you are simply happy with the one I shared?
  • Thank you for providing very complete author bios. I have had to cut them down a bit, because the format we use only provides the following information:
- Cláudia De Souza es profesora catedrática auxiliar en el Programa Graduado en Ciencias de la Información, de la Facultad de Comunicación e Información (FaCI), Universidad de Puerto Rico-Recinto de Río Piedras (UPR-RP).

- Dinah M. Wilson Fraites es estudiante doctoral en el Departamento de Estudios Hispánicos de la Universidad de Puerto Rico, Recinto de Río Piedras.

Apologies for not making that clear enough!

  • We can of course adapt the lesson title. Ideally, we could try to shorten it a little, and perhaps avoid the use of the colon (:). @jenniferisasi can certainly provide some guidance!

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Dec 18, 2024 via email

@charlottejmc
Copy link
Collaborator

Thank you for your kind words, @ClaudiaDeSouza! It's great working with you and @Dmwilsonfraites too. We're all excited about publishing your lesson. ✨

I've received the form by email, and I'll wait for @Dmwilsonfraites and @jenniferisasi to get back to us on the image, the bio and the title.

@Dmwilsonfraites
Copy link
Collaborator

Dmwilsonfraites commented Dec 18, 2024 via email •
edited by charlottejmc
Loading

@Dmwilsonfraites
Copy link
Collaborator

Dmwilsonfraites commented Dec 18, 2024 via email •
edited by charlottejmc
Loading

@charlottejmc charlottejmc mentioned this issue Dec 20, 2024
Open
6 tasks
@anisa-hawes
Copy link
Contributor

Thank you all. I will prepare this lesson for publication in early January ✨

We are in the process of setting up the new topic: metadata.

¡Felices Fiestas!

@ClaudiaDeSouza
Copy link
Collaborator

ClaudiaDeSouza commented Dec 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jenniferisasi jenniferisasi

Labels
6. Sustainability + Accessibility Español Original
Projects
Active Lessons
Status: 6 Sustainability + Accessibility
Milestone
No milestone
Development

No branches or pull requests
7 participants
@jenniferisasi @pedronilsson @anisa-hawes @semanticnoodles @charlottejmc @ClaudiaDeSouza @Dmwilsonfraites