File name structure for plants and birds 
The file name structure for objects for which we had taxonomic information on genus and species at the time of data collection, such as plants and birds, is composed as follows: 
Taking as an example the file name “Fl_TtipY”,  “Fl” corresponds to the secondary domain to which the object belongs (in this case, that of flowers).  “_”: the underscore separates the reference to the secondary domain from that to the identity information.  “Ttip” refers to the taxonomic information we had at the time of data collection. The first letter (“T”) is the initial of the generic name (in this case, Tipuana) to which the object belongs. The following letters (“tip”) are the first three letters of the specific name (in this case, tipu) to which the object belongs. Fragaria spp constitutes the only exception for this rule in this group, because we didn´t have the species taxonomic information for the measured specimen and so we used “spp” instead the first three letters of the specific name. “Y” indicates the color perceived by humans at the measured patch (in this case, yellow). 
File name structure for beetles and butterflies 
The file name structure for objects for which we had family but not genus or species taxonomic information at the time of data collection, such as beetles and butterflies, is composed as follows: 
Taking as an example the file name “Bu4_nymDBr”,  “Bu4” corresponds to the secondary domain to which the object belongs (“Bu”, butterflies) followed by a number that indicates the position of the object in the data collection sequence (in this case, the object was the fourth butterfly that was worked on).  “_”: the underscore separates the reference to the secondary domain from that to the identity information.  “nym” refers to the taxonomic information we had at the time of data collection, the family to which the insect belongs (in this case, Nymphalidae).  “DBr” indicates the color perceived by humans at the measured patch (in this case, dark brown). 
File name structure for stones (rocks and minerals)
Taking as an example the file name “S23_crisBl”,  “S23” corresponds to the secondary domain to which the object belongs (“S”, stones) followed by a number that indicates the position of the object in the data collection sequence (in this case, the object was the twenty-third stone that was worked on). “_”: the underscore separates the reference to the secondary domain from that to the identity information. “cris” refers to the identity information we had at the time of data collection, the general identification of the rock or the mineral (in this case, the mineral name chrysocolla). “Bl” indicates the color perceived by humans at the measured patch (in this case, blue). 
Special cases 
Name structure for repeated objects 
The file name structure for objects that were collected and measured more than one time (i.e., repeated objects), is composed as follows: 
Taking as an example the file name “F_Mpar1Y”, “F” > Secondary domain (Fruits); underscore; “Mpar” > taxonomic information (“M” refers to the generic name Musa and “par” to the specific name paradisiaca); “Y” > patch perceived color (yellow). The addition is the number “1” after the taxonomic information and before the color code, which enumerates the repeated measured objects. 
Name structure for leaves from plants with flowers of different colors 
The file name structure for leaves that correspond to the same plant species but with flowers of different colors, is composed as follows: 
Taking as an example the file name “L_Bspe_R_G”, “L” > Secondary domain (Leaves); underscore; “Bspe” > taxonomic information (“B” refers to the generic name Bougainvillea and “spe” to the specific name spectabilis); the final “G” > patch perceived color (green). The addition is the color code “R” between underscores, after the taxonomic information and before the color code, which indicates the color of the plant's flower from which the leaf was measured (in this case, red). 
Name structure for butterflies and birds with iridescent colors 
The file name structure for butterflies and birds that have iridescent colors that we measured, is composed as follows: 
Taking as an example the file name “B_CcorDG_45”, “B” > Secondary domain (Birds); underscore; “Ccor” > taxonomic information (“B” refers to the generic name Colibri and “spe” to the specific name coruscans); “DG” > patch perceived color (dark green). The addition is the number (“45” in this case, but it should also be an equivalent file with “0”) after a second underscore, at the end of the name, which indicates that this patch was measured with the spectroradiometer positioned at two different lateral angular orientations (at 45 and 0 degrees) relative to the sample. 
Name structure for birds with data for males and females 
The file name structure for those bird species that are represented for both male and female specimens is composed as follows: 
Taking as an example the file name “B_BcinDBrF”, “B” > Secondary domain (Birds); underscore; “Bcin” > taxonomic information (“B” refers to the generic name Batara and “cin” to the specific name cinerea); “DBr” > patch perceived color (dark brown). The addition is the capital letter (“F” in this case, but it should also be another/s file/s for this species with a final “M”), at the end of the name, which indicates that this file corresponds to a female specimen. 
All files of bird specimens that have no indication of sex correspond to data from male specimens. 
