Issue #184 - Add investigation:Technician role class #186
Conversation
vulnmaster
added
Community-Vote
|
Thank you @sbarnum for noting |
|
@vulnmaster , this PR will need to be rebased to |
|
Alex - can you do this for me? I probably need to refork CASE to re-align
to the current Main.
Vulnmaster
…On Tue, Dec 2, 2025 at 6:04 PM Alex Nelson ***@***.***> wrote:
*ajnelson-nist* left a comment (casework/CASE#186)
<#186 (comment)>
@vulnmaster <https://github.com/vulnmaster> , this PR will need to be
rebased to develop. It was started from master. This will need a Git
force-push to correct. Do you wish to do that, or would you like me to?
—
Reply to this email directly, view it on GitHub
<#186 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIHKPF3X7NBY2Z4B3BFRQT37YLHRAVCNFSM6AAAAACJ5FPCM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBUGMYDONJTGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The issue is not a stale repository. The issue is the CASE GitHub repository is one of the CDO repositories that uses Git-Flow, as described here. This needed to be started from I can do this from command-line if you checked the "Allow maintainers to modify" box (I forget the wording, it's on this page visible to you). I might be able to do this from the GitHub interface - I forget what a certain Edit feature does. I'll give it a try, maybe two, now. |
|
Ok, the button only did half of what it needed to do. Force-pushing in a moment. |
Adds investigation:Technician as a new role class to the CASE investigation ontology, addressing Issue casework#184. A technician is a forensics role focused on technical tasks during investigations, such as evidence collection, preservation, processing, initial analysis, and repair. Changes: - Added investigation:Technician class definition to investigation.ttl - Created comprehensive test example (technician_role_PASS.json) demonstrating Identity-role-performer pattern with temporal tracking - Updated test suite (Makefile and test_validation.py) - Updated ChangeLog The implementation follows the established pattern used by other role classes (Attorney, Examiner, Investigator, Subject) and maintains backward compatibility. Tests demonstrate: - Technician role instances with appointment dates (startTime) - Identity linked to Technician role via uco-core:role - Technician role as performer of InvestigativeAction - Integration with Investigation, File, and ProvenanceRecord All SHACL validation tests pass. Closes casework#184
ajnelson-nist
force-pushed
the
184-addition-of-investigationTechnician-role-class
branch
from
34ec2fa to
9d5b625
Compare
|
Ok. Further revisions coming in light of the test review done prior to this morning. |
No effects were observed on Make-managed files. Signed-off-by: Alex Nelsin <alexander.nelson@nist.gov>
References: * casework#184 Signed-off-by: Alex Nelsin <alexander.nelson@nist.gov>
Note this patch does not tie the role to the action, nor does it define an investigation to tie the action, person, role, relationship, etc., together, due to needing to address broader design issues pertaining to `uco-role:Role`, some of which are under exploration in CASE-Examples Issue 155. This patch also fixes a typo'd concept - `uco-core:Identity` was used instead of `uco-identity:Identity`. This was not revised to `uco-identity:Person` in light of discussion going on in UCO Issue 652. No effects were observed on Make-managed files. References: * casework#184 * casework/CASE-Examples#155 * ucoProject/UCO#652 Signed-off-by: Alex Nelsin <alexander.nelson@nist.gov>
|
@plbt5 - May this PR have your review, esp. with an eye to patch bed10f7 and its commit message? |
3 participants
Adds
investigation:Technicianas a new role class to the CASE investigation ontology, addressing Issue #184.A technician is a forensics role focused on technical tasks during investigations, such as evidence collection, preservation, processing, initial analysis, and repair.
Changes:
investigation:Technicianclass definition to investigation.ttlThe implementation follows the established pattern used by other role classes (Attorney, Examiner, Investigator, Subject) and maintains backward compatibility.
Tests demonstrate:
All SHACL validation tests pass.
This is a low risk addition to CASE.
Ready for solution review.