A Week 4 search log records databases, exact strings, filters, dates run and results retained at each stage, in enough detail for another reader to repeat it. Searches like "inhe 3003 week 4 assignment example", "inhe3003 week 4 sample" and "inhe 3003 week 4 example" land here.
What a finished INHE 3003 Week 4 search log looks like
The finished log is closer to a record than to an essay, and its density is the point. Each database appears with the date it was searched, since holdings change. Search strings are reproduced exactly, including operators, truncation symbols and the way terms were combined, rather than described in prose. Filters are listed as applied. The counts at each stage are recorded, along with how many items moved forward and on what basis items were set aside. A short reflective passage follows the record and explains what was changed mid process and why, which is where the analytical credit sits. Nothing in the log presents a smooth path, because real searching is iterative and the log is expected to show it.
How a INHE 3003 Week 4 example is structured
A table or a structured list carries the record, and prose surrounds it lightly. An opening paragraph states the question the search served, usually the structured question from the previous week. The record follows, one block or row per database, with columns for date, exact string, filters, results returned and results retained. Screening criteria are stated once, before or immediately after the record, so that decisions can be checked against them. A reflection paragraph closes the piece and covers the revisions made during searching. If the prompt calls for it, the items carried forward are listed at the end in the classroom's citation style. Prose is kept minimal throughout, because a log padded with narrative about the difficulty of searching buries the record an assessor is trying to read. Abbreviations used inside cells are defined once.
The question the search served
One paragraph tying the log to the structured question it was built from. Logs that begin with the first database entered leave the assessor unable to judge whether the terms were appropriate, since appropriateness is relative to a question.
Strings reproduced, not described
The exact text entered, operators and truncation included. A described search cannot be repeated, and repetition is the criterion. This is the difference between a log and a summary of having searched, and assessors read it first.
Dates, filters and holdings
The date each database was searched and the filters applied. Databases change, so an undated entry cannot be reproduced even when the string is perfect. Filters appear as they were actually set, since one the writer meant to use but never applied changes the count that follows.
What was set aside, and why
Stated screening criteria and the counts moving through each stage. Records showing retention without stating the basis for exclusion cannot be audited, and the transparency criterion reads exactly this passage.
The revisions made mid process
A reflective close on what was changed and why, whether a term that returned nothing or a filter that removed too much. This passage carries the analytical credit, and logs that present searching as a straight line usually lose it.
Where marks go in INHE 3003 Week 4
The largest deductions follow from described rather than reproduced searches. A log saying that the writer searched a database for terms related to the topic has recorded an activity rather than a method, and no amount of tidy formatting recovers the reproducibility criterion. Missing dates are the second most common deduction and the easiest to avoid. The third weight sits on screening: counts recorded without stated criteria show a funnel with no rules, which cannot be checked. The reflection is where stronger logs pull ahead, since a record that shows a term being revised, and explains what prompted it, demonstrates judgment the bare record cannot. Presentation carries a small weight of its own, since a record crammed into paragraphs rather than laid out in rows is technically complete and practically unusable.
Get a INHE 3003 Week 4 example written to your instructions
What any real search returns depends on the holdings your library carries, so this sample models the record and its reasoning rather than standing in for searching you do. Send the question the search serves, with the assignment instructions and rubric beside it, and a custom log follows inside 24-48h, first at no cost.
INHE 3003 Week 4 questions, answered
Do the search strings really need to be copied exactly?
Yes, and this is the criterion the assignment exists to teach. Operators, truncation symbols and the grouping of terms all change what a database returns, so a described search cannot be repeated by anyone. Copying the string exactly costs nothing and satisfies the requirement that carries the most weight on the piece.
What if a search returns nothing usable?
Record it, with the string and the date, and keep it in the log. An empty result is a real finding about how the question was worded and often explains the revision that followed. Logs that quietly delete unproductive searches present a path that never happened, which undercuts the transparency the assignment is scored on.
How many databases should the log cover?
Your prompt usually specifies, and where it does not, two or three searched properly beats a longer list searched shallowly. What matters is that each entry is complete enough to repeat and that the choice of databases suits the question. A log covering many databases with partial records scores below a shorter one that could actually be reproduced.