> For the complete documentation index, see [llms.txt](https://derek-johnson-1.gitbook.io/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://derek-johnson-1.gitbook.io/welcome/freshman/system-140/week-13/information-literacy-integration_21.md).

# Information Literacy Integration\_21

### Information Literacy Integration <a href="#fulo0673bzv6" id="fulo0673bzv6"></a>

**Preparation: Please refer to the SYS-140 - Week 12 Lab 1 assignment for this submission.**

**The questions below are in context to 3 above (the process explorer exercise) where you had to lookup what “Private Bytes” and “Working Set” mean and from 3 under Autoruns where you found information about 3 processes you didn’t (or did) recognize. Research those terms and then consider the terms below and the following questions.**

There are some important aspects to accessing information that one should be aware. Some to explore are: Filter Bubbles and Information Gatekeepers.

1. Knowing that your prior search history can impact your search results, did you change your search strategy this time around? (NOTE: Did the discussion impact how you search for information?)

Yes, after looking into filter bubbles and the bias a search algorithm can have. The second time around I added specific key words to my search such as "cybersecurity", "computer systems", and "memory" when looking into private bytes and working set.

1. How might the "Filter Bubble" impact your research on a topic? (NOTE: Think of this in context to what courses you are studying and the types of searches you’ve been performing relative to those courses.)

When searching for what different acronyms stand for, the google search engine because of my past search history usualy gives me the answer related to information technology or security even if that is not the definition I want. For example ROM in IT stands for read only memory and in medical science it stands for range of motion. If your search history is largely medical questions (if you were a med student) looking up ROM would most likely return the medical meaning not the IT meaning.

1. When seeking out information, do you go to sources you were already familiar with? Do you try out different websites or sources than the one you typically use? (NOTE: The latter question is in context to since you learned about filter bubbles and information gatekeepers.)

Search engines can have biases and give you websites you commonly use. To get around this an individual can try to use different websites they haven't used before as long as they are creditable.

1. When selecting your resources, how do you know the site you were using was reputable or credible? (NOTE: Provide logical reasoning for why you selected those sites AND found those to be reputable and credible.)

Checking the domain name is good way to tell if it's a legitment website. If it is a .org or .gov it most likely is published from a reputable source. You can also check the author of the article if it has one. You can search the reputation of their past work. You can also check the last time the website was edited to see if it has updated information.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://derek-johnson-1.gitbook.io/welcome/freshman/system-140/week-13/information-literacy-integration_21.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
