<WRAP centeralign round box>
<WRAP><color red><fs 200%>Corning Community College</fs></color></WRAP>
<WRAP><fs 150%>CSCS1730 UNIX/Linux Fundamentals</fs></WRAP>
</WRAP>

======Project: Data Archiving and Compression (dac0)======

=====Objective=====
Reference technical documentation to locate and operate particular tools to aid you in accomplishing a task. Collaboratively construct an informative document to detail how one can prepare to start upon this process.

=====Prerequisites=====
To successfully accomplish/perform this project, the listed resources/experiences need to be consulted/achieved:

  * ability to read the manual pages and use the information therein
  * ability to copy, move, and list files
  * ability to navigate around the filesystem

=====grabit=====
As part of this activity is to test your ability to navigate around the filesystem and manipulate files on your own, there is no grabit configured for this project.

=====EDIT=====
You will want to go [[/notes/unix/spring2024/projects/dac0|here]] to edit and fill in the various sections of the document:

  * [[/notes/unix/spring2024/projects/dac0|https://lab46.g7n.org/notes/unix/spring2024/projects/dac0]]

{{page>notes:unix:spring2024:projects:dac0&nouser&nodate&nomdate&editbtn}}

=====On your development system=====
On your development system, I want you to do the following:

  - Figure out the format of the files, and read up on the available tools for manipulating them
  - Install any needed tools to accomplish the task of accessing the information contained within
  - Extract the contents of the archive and study it (contents will extract to the current working directory, so you WILL want to be in a custom project directory)
  - Analyze the files extracted from the archive. Each file will ultimately be contextually readable plain text (in English), but some may be encoded or compressed or otherwise manipulated and will need further processing to get to the final readable state.
    * Once in their readable states, name the files **a**, **b**, **c**, **d**, **e**, **f**, **g**, **h**, in order of their file sizes (in bytes), from least to greatest.
  - Place these single-lettered files in a new **tar** archive called **result.tar** (files should be added to the archive in the current directory, do not embed any directory information in the archive).
  - Compress it (using **maximum** compression) with **gzip**(**1**); it should now be called **result.tar.gz**
    * you are going to submit this archive
  - In addition to the created archive, you will also submit a text file named **dac0.steps** which will contain step-by-step command-lines used to copy, extract, manipulate, rename, create a new archive and compress **result.tar.gz** (document from the point of having the copied files in place on your development system).
    * you do NOT need to include and repository, verify, or submit commands, JUST those steps for accomplishing the core task of the files in the project to stated specifications. 
    * The file should JUST contain the exact commands you used, in order from start to finish. If you'd like to add any additional commentary, prefix it with a # sign.
      * Commands should be left justified, one command-line per line (lines can wrap).
	  * Do NOT number your steps. Just place the command-line incantations utilized, one after the other.

=====Verification=====
One of the tests I will perform for output compliance of your code will involve comparing your program's output against a range of input values, to see if they all output in conformance with project specifications.

I will make use of a checksum to verify exactness.

You will need to run this from your dac0 project directory, where your individual a-h files are located.

You can check your project by typing in the following at the prompt (on lab46):

<cli>
lab46:~/src/SEMESTER/unix/dac0$ filechk unix dac0
</cli>

If all aligns, you will see this:

<cli>
==========unix/dac0 whole file comparison=========================================
 For the file: a
     you want: cca000c9cb8a5c134bed61154a7907ba
     you have: cca000c9cb8a5c134bed61154a7907ba MATCH

 For the file: b
     you want: c8136ca761229bad59497021a8f425af
     you have: c8136ca761229bad59497021a8f425af MATCH

 For the file: c
     you want: d6db0da4b084fff4b255ae7a4e95ed62
     you have: d6db0da4b084fff4b255ae7a4e95ed62 MATCH

 For the file: d
     you want: dadd5272203fa77b80f26cf355e6e833
     you have: dadd5272203fa77b80f26cf355e6e833 MATCH

 For the file: e
     you want: af095aeaaf55a8a3b351a921baebc9e7
     you have: af095aeaaf55a8a3b351a921baebc9e7 MATCH

 For the file: f
     you want: 84d0fd81532fac6c743c8054f76f0270
     you have: 84d0fd81532fac6c743c8054f76f0270 MATCH

 For the file: g
     you want: c36a56a9ab8190e4d007bd16e377639a
     you have: c36a56a9ab8190e4d007bd16e377639a MATCH

 For the file: h
     you want: 226c53b09f112cf7323cd5263302ea95
     you have: 226c53b09f112cf7323cd5263302ea95 MATCH

</cli>

If something is off, your checksum will not match the dac0 checksum, and verification will instead say "**MISMATCH**", like follows (note that a mismatched checksum can be anything, and likely not what is seen in this example):

<cli>
==========unix/dac0 whole file comparison=========================================
 For the file: a
     you want: cca000c9cb8a5c134bed61154a7907ba
     you have: cca000c9cb8a5c134bed61154a7907ba MATCH

 For the file: b
     you want: d8136ca761229bad59497021a8f425af
     you have: c8136ca761229bad59497021a8f425af MISMATCH

 For the file: c
     you want: d6db0da4b084fff4b255ae7a4e95ed62
     you have: d6db0da4b084fff4b255ae7a4e95ed62 MATCH

 For the file: d
     you want: dadd5272203fa77b80f26cf355e6e833
     you have: dadd5272203fa77b80f26cf355e6e833 MATCH

 For the file: e
     you want: af095aeaaf55a8a3b351a921baebc9e7
     you have: af095aeaaf55a8a3b351a921baebc9e7 MATCH

 For the file: f
     you want: 84d0fd81532fac6c743c8054f76f0270
     you have: 84d0fd81532fac6c743c8054f76f0270 MATCH

 For the file: g
     you want: d36a56a9ab8190e4d007bd16e377639a
     you have: c36a56a9ab8190e4d007bd16e377639a MISMATCH

 For the file: h
     you want: 226c53b09f112cf7323cd5263302ea95
     you have: 226c53b09f112cf7323cd5263302ea95 MATCH

</cli>

=====SUBMISSION=====
To be successful in this project, the following criteria (or their equivalent) must be met:

  * Project must be submit on time, by the deadline.
    * Late submissions will lose 33%  credit per day, with the submission window closing on the 3rd day following the deadline.
  * Track/version your projects files in your lab46 semester repository
  * Submit a copy of your final archive to me using the **submit** tool.

====Submit Tool Usage====
Let's  say you  have completed  work  on the  project, and  are ready  to
submit, you  would do the following:

<cli>
lab46:~/src/SEMESTER/DESIG/PROJECT$ submit DESIG PROJECT file1 file2 file3 ... fileN
</cli>

A less abstract instantiation of the above (to help you transition):

<cli>
lab46:~/src/SEMESTER/unix/dac0$ submit unix dac0 result.tar.gz dac0.steps
Submitting unix project "dac0":
    -> result.tar.gz(OK)
    -> dac0.steps(OK)

SUCCESSFULLY SUBMITTED
</cli>

You should get some sort of confirmation indicating successful submission
if all went according to plan. If  not, check for typos and or locational
mismatches.

=====RUBRIC=====
I'll be evaluating the project based on the following criteria:

<code>
26:dac0:final tally of results (26/26)
*:dac0:archive submitted [2/2]
*:dac0:archive has correct name of result.tar.gz [2/2]
*:dac0:archive is max compressed with gzip [2/2]
*:dac0:archive is a tar archive [2/2]
*:dac0:archive extracts into current directory [2/2]
*:dac0:archive contains 8 english readable files [2/2]
*:dac0:archived files are named a-h [2/2]
*:dac0:archived files named in order of size [2/2]
*:dac0:instructions submitted in text file [2/2]
*:dac0:instructions in file named dac0.steps [2/2]
*:dac0:dac0.steps contains list of instructions for accomplishing task [2/2]
*:dac0:dac0.steps instructions are accurate and correct [2/2]
*:dac0:dac0.steps any extra information after hash mark [2/2]
</code>

====Pertaining to the collaborative authoring of project documentation====

  * each class member is to participate in the contribution of relevant information and formatting of the documentation
    * minimal member contributions consist of:
      * near the class average edits (a value of at least four productive edits)
      * near the average class content change average (a value of at least 1024 bytes (absolute value of data content change))
      * no zero-sum commits (adding in one commit then later removing in its entirety for the sake of satisfying edit requirements)
    * adding and formatting data in an organized fashion, aiming to create an informative and readable document that anyone in the class can reference
    * content contributions will be factored into a documentation coefficient, a value multiplied against your actual project submission to influence the end result:
      * no contributions, co-efficient is 0.50
      * less than minimum contributions is 0.75
      * met minimum contribution threshold is 1.00

====Additionally====

  * Solutions not abiding  by spirit of project will be  subject to a 50% overall deduction
  * Solutions  not  utilizing descriptive  why and  how comments  will be subject to a 25% overall deduction
  * Solutions not utilizing indentation to promote scope and clarity or otherwise maintaining consistency in code style and presentation will be subject to a 25% overall deduction
  * Solutions not organized and easy to  read (assume a terminal at least 90 characters wide, 40 characters tall)  are subject to a 25% overall deduction