How to keep a source-update log for nail knowledge
A source-update log records when a reference was checked, what changed and which product records or claims depend on it. Keep the source’s publication or revision date separate from the date you accessed it. A changed webpage and a changed underlying document are different events.
KEY TAKEAWAYS
- Separate source date, access date and record revision.
- Record the relevant passage, not only the URL.
- A changed page needs claim review before rewriting the conclusion.
Create the source entry
Start one entry using the complete log inventory below, linking it to the supporting passage. If no source date is supplied, use unknown. An access date is a record of your check, not permission to invent a publication date.
Distinguish document and database revisions
HSA explains that an SDS issue or revision date appears on its first page and that Section 16 can describe the changes. CosIng distinguishes current active data from historical not-active data. Put these different version signals in separate fields. A saved-file timestamp or website footer is not, by itself, the document’s revision date. [1][2]
Log the change before revising the record
Use one complete log row: source title; publisher; source URL; source date and stated date kind; access/check date; previous document/revision; current document/revision; database-entry status; previous passage locator; current passage locator; change type; affected product record or claim; local record revision; required action; replacement-file link; closing status. The local record revision is your own version label for the affected record, separate from the source’s date or document revision. Mark “not applicable” where no previous version or replacement file exists; keep unknown values explicit. Useful change types are moved URL, new revision, corrected wording, changed scope and unavailable source. A moved page may require only a link repair; a changed result requires checking the conclusion that depended on it.
Close the record with an action and status
Close each row with one proposed status: “no relevant change” when the check finds no relevant change in the passage or its applicability; “link repaired” when the URL is corrected without a relevant content change; “record revised” when the affected record has been updated and its local revision recorded; “awaiting clarification” when a relevant question remains unresolved. Link to any replacement file, preserve the old version and name the fields or claims affected. Status examples: a moved URL with an unchanged document closes as “link repaired”; a revised applicability scope retains “awaiting clarification” until the affected product record is checked. Record the actual check date even when nothing changed.
Article Sources
- Health and Safety Authority, Ireland — Questions and Answers
Primary source
Ireland’s regulator Q&A on REACH safety data sheets. Format answer: 16 headings, Section 1 identification and issue/revision date on the first page. Update answer: changes may be identified in Section 16. Separate provision and exemption answers explain the scope of SDS supply duties.
- European Commission — Cosmetic ingredient database
Primary source
Overview and search-description passages: common ingredient names, CAS/ELINCS/EINECS identifiers, records since 1976 and active versus historical entries. Important notice: the database is informative and non-binding; inclusion is not ingredient-use approval. Overview reviewed, without testing the search engine or individual records.
Written and reviewed with AI assistance using the linked sources. No hands-on product testing or independent specialist review was performed.
Commercial resource from our ecosystem
Professional nail materials and tools with NailMarket.eu — a shop in our ecosystem.
NailWiki, BELOM, NailMarket, BELOM App and NaNails are projects of BELOM Group OÜ, as identified by the owner. Molokom catalogue images are supplied through our NaNails shop; this commercial relationship is not independent product-test evidence.
