Skip to content

Data management: naming conventions and folder structure

Jill Walker Rettberg edited this page Aug 15, 2019 · 2 revisions

Sites for sharing data and research materials

  • Sharepoint: For saving data exports, project files, research notes, abstracts, etc privately within the group.
  • Github: Wiki for documentation of coding schema (public), Issue tracker for development of database and coding schema.
  • UiB website, Researchgate, Tumblr, Instagram etc for dissemination and public sharing.

Naming conventions for files in Sharepoint:

(coming soon)

Data exports

Naming database views for data exports

Start with the type of node you are exporting data about, then the fields you are exporting. Put two hyphens after the node type.

Nodetype--field1-field2-field3

so for instance:

Situation--sentiments-techused

The machine-readable name has to be the same but with underscores.

All views/data exports should be tagged machinevision.

The menu path or URL should follow the same basic pattern, e.g.

data/situations/technologies-doing-functioning-context-owner-viewed Or as shown in this screenshot:

Imports into excel to get ready for Gephi:

Rename the sheet with the original import Full dataset downloaded and set it too protected. At the top of the sheet, put the URL of the data export view in 14pt, bold. Below this, type the date. Then import the CSV file so it starts in cell A3. It should look like this:

Then create a separate sheet where you work with the data, removing unnecessary columns, removing duplicates etc. Title this "selected data" and protect it. Make more sheets if you are trying to do different things. The important thing is not to tamper with the full dataset, so we always know what the original data was.

When you are happy with the dataset, create the nodes and edges sheets and name them Nodes and Edges. These are the sheets you will import into Gephi, so they should be first.

Clone this wiki locally