CRAWDAD metadata is a description for CRAWDAD data, tools, and related authors and papers. Here is a sample metadata and following will be how to read and navigate the metadata.
Metadata structure (example)
- [Data]
- [Dataset] ucsd/sigcomm2001 (v. 2002-04-23) [what's new] [version history]
- [Traceset] ucsd/sigcomm2001/snmp (v. 2002-04-05)
- [Trace] ucsd/sigcomm2001/snmp/Stations (v. 2002-04-05) [download 4 MB zip]
- [Trace] ucsd/sigcomm2001/snmp/AP_Mibtree (v. 2002-04-05) [download 59 MB zip]
- [Traceset] ucsd/sigcomm2001/tcpdump (v. 2004-11-09)
- [Trace] ucsd/sigcomm2001/tcpdump/08292005 (v. 2002-04-23) [what's new][download 267 MB gz]
- [Tools]
- [Tool] ucsd/sigcomm2001/tool/snmputil.exe (v. 2002-04-05) [download 73 KB exe]
- [Tool] ucsd/sigcomm2001/tool/extract.pl (v. 2002-04-05) [download 3 KB pl]
- [Authors]
- [Author] Anand Balachandran
- [Author] Geoffrey M. Voelker
- [Author] Paramvir Bahl
- [Author] P. Venkat Rangan
- [Papers]
- [Paper] meng-flows
- [Paper] balachandran-behavior
CRAWDAD metadata has four categories: data, tools, authors, and papers. As shown in the above example, metadata structure represents a hierarchy in each category. For example, there is a hierarchy of dataset, traceset, and trace in data category in that order. The other categories - tools, authors, and papers - have only one level of hierarchy.
- Hiearchy in data category : A dataset is a set of wireless network data, collected by the same organization on the same type of network with some temporal locality (e.g., without a long time gap). For example, the dataset in the above example is a set of data which were collected by University of California, San Diego on the 802.11 network of a conference held in the campus during three days. A traceset is a set of traces that were collected using the same measurement technique, e.g., snmp, tcpdump, syslog, etc. A dataset can contain multiple tracesets, and a traceset can contain multiple traces.
- Hierarchical naming : Naming in data category follows the hierarchy of dataset, traceset, and trace, by joining them with "/". For example, the dataset "ucsd/sigcomm2001" has two tracesets, "ucsd/sigcomm2001/snmp" and "ucsd/sigcomm2001/tcpdump", which represent trace sets collected using snmp and tcpdump, respectively. Likewise, the traceset "ucsd/sigcomm2001/snmp" contains two "downloadable (by clicking [download] link)" traces, "ucsd/sigcomm2001/snmp/Stations" and "ucsd/sigcomm2001/snmp/AP_Mibtree". More information on each entity (dataset, traceset, or trace) can be obtained by clicking its name.
- Other categories: represents the tools, authors, and papers which are related with the entities shown in data category.
- Versions: We assume that only the entities in data and tools categories have versions: the entities in the other categories have no version. We use the release date as a version number. For example, the version number "v. 2004-04-23" of the dataset "ucsd/sigcomm2001" indicates that the dataset was released on April, 23, 2004. For browsing all the versions, you can click "[version history]" link. If you want to know the changes from the previous version, you can click "[what's new]" link.
