A finished EN 111 Unit 2 database search log: databases, strings, operators, limiters and result counts recorded in order, with failed attempts left in. Searches like "en 111 unit 2 assignment example", "en111 unit 2 sample" and "en 111 unit 2 example" land here.
What a finished EN 111 Unit 2 database search log looks like
The log is a table or a numbered sequence, and it is dull on purpose. Each row names the database searched, the exact string entered, any operators used, the limiters applied, and the number of results returned. A column beside each entry says what the writer concluded from that count and what changed in the next attempt. The sequence runs in the order the searching happened rather than tidied into a clean path, so a reader watches a term abandoned, a synonym tried, a date limit applied and the count dropping. Searches returning nothing are logged with the same detail as productive ones. A short closing paragraph names the strategy that worked and the two or three items it retained, usually with their citations.
How a EN 111 Unit 2 example is structured
Order is chronological because the unit grades a process, and a log sorted by database or by usefulness destroys the reasoning it was built to preserve. Each row is self-contained, carrying the string and the count together, since a term listed without its result says nothing about whether it worked. The note on what changed sits with the entry rather than in a summary, so a reader follows one decision at a time instead of reconstructing them all at the end. Failed searches stay in position, because a log showing only productive attempts describes a process nobody ran. The retained items come last and briefly, as this deliverable is about the route rather than the destination, and a log turning into a source list halfway through has changed genre.
One row per search, as entered
Each attempt records the database, the string typed and the count returned, so another person could repeat that search unchanged.
Operators and limiters recorded separately
The words joining the terms and the filters applied to the results are logged as distinct choices rather than folded together.
Result counts beside every attempt
The number returned appears with each entry, since a term with no count attached says nothing about whether it worked.
Failed searches kept in sequence
Attempts returning nothing stay where they happened, because a log showing only productive searches describes a process that was never run.
What changed and why, per entry
A short note beside each row says what the count prompted, which is the reasoning the criterion is actually reading for.
Retained items named briefly at the end
The closing lists what survived without annotating it, since this deliverable is the route rather than the sources it reached.
Where marks go in EN 111 Unit 2
Search logs lose points by being written afterward. A log of five searches that each narrowed neatly, with no dead ends anywhere, reads as a reconstruction and markers treat it as one. Entries with terms but no result counts remove the only measure of whether anything worked. Strings recorded loosely, so a reader cannot tell what was actually typed, make the search unrepeatable, and repeatability is usually stated in the criteria. Logs listing databases without saying which was searched for what treat them as interchangeable. Operators described in the abstract rather than shown inside a string prove nothing. Logs that quietly become a bibliography halfway through have abandoned the deliverable. One database searched once is a search, not a strategy.
Get a EN 111 Unit 2 example written to your instructions
Two attachments cover this unit: the EN 111 instructions for Unit 2 and the rubric your classroom posts, plus your question if you already have one. We write a custom example logging each attempt with its string, operators, limiters and count, dead ends included, and closing on what the searching retained. First custom sample free, returned in 24 to 48 hours.
EN 111 Unit 2 questions, answered
Do I have to log searches that found nothing?
Those are often the valuable rows. A search returning zero results tells you that a term is not how the literature names the idea, and recording it shows the reasoning the criterion is reading for. Logs consisting only of successful attempts look assembled after the fact, which costs more than an untidy record of what actually happened.
Which database should the log cover?
Whichever your instructions name, and more than one where the choice is open. A general multidisciplinary database and a subject-specific one return different things for the same string, and showing that difference is part of what a log demonstrates. Your library guides usually say which databases cover which fields, and the log is stronger for naming why each was chosen.
Can the log include searches I ran at work?
Keep it to the library resources your classroom expects. An employer's internal system, a subscription your organization pays for under its own agreement, or a search of company records cannot be repeated by your instructor and may not be yours to describe. Academic databases are checkable, which is exactly what a log submitted for points has to be.