General questions and discussion

[jawalsh]

This is a space for asking general questions about the course. If you have questions or topics that may be of interest to many people in the class, feel free to post them here.

[heidi-y]

Hi @jawalsh and @aewingate, on my end it looks like the LinkedIn Learning video for this week is stuck behind a paywall. Not sure if I missed something about that in class. Any help accessing it would be appreciated. Thanks :)

[jawalsh]

If you access LinkedIn Learning through https://one.iu.edu/ and try again, I think it will work. Let us know!

[heidi-y]

Yes, that worked, thank you!!

[aprilmurb]

Hi @jawalsh and @aewingate, for the Week 4 tasks, I'm kind of confused by the directions for installing tesseract on Mac. What does "homebrew" refer to?

[aewingate]

I am a PC person, so this is my shot at what it means: Homebrew is a program that helps you install Unix programs (a type of program you can run on the command line/terminal). So you want to open a macOS Terminal by either:

• Click the Launchpad icon in the Dock, type Terminal in the search field, then click Terminal.
• In the Finder , open the /Applications/Utilities folder, then double-click Terminal.

Then you will paste in /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" and hit "Enter"
That should install Homebrew. Once the Terminal has finished installing Homebrew, then paste brew install tesseract into the Terminal and hit "enter" to install Tesseract.

Let me know if that doesn't work!

[jawalsh]

I updated the Week 4 page:

Homebrew is package manager that simplifies the process of installing Unix software on your Mac. Installation instructions are available at https://brew.sh/.

John

[jawalsh]

I updated the Week 4 page: * Homebrew<https://brew.sh/> is package manager that simplifies the process of installing Unix software on your Mac. Installation instructions are available at https://brew.sh<https://brew.sh/>. John On Sep 15, 2022, at 11:26 AM, aprilmurb ***@***.***> wrote:  This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources. Hi @jawalsh<https://github.com/jawalsh> and @aewingate<https://github.com/aewingate>, for the Week 4 tasks, I'm kind of confused by the directions for installing tesseract on Mac. What does "homebrew" refer to? — Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEXWOMVV5RS7ELO3VXB5CTV6M53RANCNFSM57UGUXTA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[aewingate]

Hi everyone,

I got a few questions by email about the metadata application profile assignment, so I wanted to answer them here:
1. Do we need to have the longer descriptions that Alex has of her elements?
The first thing to consider in the directions for the assignment is: "Select, customize, and document an element set and element specifications that will meet those functional requirements and connect the intended users to the digital content in the organizational context."

Technically, no you do not have to include those more in-depth descriptions. However, think about the hypothetical audience (other than me and Prof. Walsh) for the MAP. This is documentation to explain to others how you did your metadata and/or explain to others how they should input the metadata for your collection. If you look at the examples near the end of Chapter 12, most of the professional MAPs there include a description of each element because it's useful explanatory information. Some elements are quite obvious (e.g. title), but others may not be to someone other than yourself. It's good to include that kind of thing to get everyone on the same page.

And remember, your MAP does not have to follow exactly how I structured it. The important thing is to document how you are designing this clearly. What I did may not work for you!

2. How should we indicate our functional requirements?

You can do this in sentences, tables, bullets, etc. Whatever makes sense to you. The important thing is to express what concrete actions you want your users to be able to do (e.g., browsing by subjects; navigating by place on a map) and which of your elements will allow them to do that.