uploading hierarchical data to firebase from google sheets - firebase-realtime-database

Question

I am trying to upload data to firebase where the structure of my database is hierarchical. How can I manage that structure in google sheets. I have been looking for this on many websites but found nothing.
Please help. Here is the structure of my firebase
update 1
after trying the suggested model #2, i am unable to upload repeated data lines. here is my google script:
var secret = 'in2HGSgx7uMtOvqhpIzUf1tPCI97cwnzGmae5Dg1'
function getFirebaseUrl(jsonPath) {
return (
'https://sheetsdemo-8d0e9.firebaseio.com/ ' +
jsonPath +
'.json?auth=' +
secret
)
}
function syncMasterSheet(excelData)
var options = {
method: 'put',
contentType: 'application/json',
payload: JSON.stringify(excelData)
}
var fireBaseUrl = getFirebaseUrl('TimeTable')
UrlFetchApp.fetch(fireBaseUrl, options)
}
function startSync() {
var sheet = SpreadsheetApp.getActiveSheet()
//Get the number of rows and columns which contain some content
var [rows, columns] = [sheet.getLastRow(), sheet.getLastColumn()]
//Get the data contained in those rows and columns as a 2 dimensional array
var data = sheet.getRange(1, 1, rows, columns).getValues()
var dataObject = {};
for (var i = 0; i < data.length; i++) {
var dataRow = data[i];
// in cell A I have my item name and in B i have my item code
var day = dataRow[0];
var section = dataRow[1];
var course_id = dataRow[2];
var time = dataRow[3];
var course_title = dataRow[4];
var teacher = dataRow[5];
// we then create our first property on our data object dataObject.code- name : { }
dataObject[section + day] = {
day: day,
section: section,
course_id: course_id,
time: time,
course_title: course_title,
teacher: teacher
};
syncMasterSheet(dataObject)
}
}

Answer 1

I know of of two models for storing hierarchical data in a table/spreadsheet:
to indent each level into a next column, or
to add a parent ID to each row.
indent each level into a next column
This is the most direct mapping of what you've shown to a table:
1 2 3 4 5 6
A TIME TITLE TEACHER
B Monday
C FA16....
D COURSE1 11:00 CCN OWAIS
E COURSE2 11:30 CG MAM
An advantage of this is that it's fairly easy to read visually. But a disadvantage is that it's easy for the column titles to get out of whack if your data is not completely homogenous.
add a parent idea to each row
In this model your flatten/normalize the data:
1 2 3 4 5 6
A DAY CODE1 COURSEID TIME TITLE TEACHER
B Monday FA16.... COURSE1 11:00 CCN OWAIS
C Monday FA16.... COURSE2 11:30 CG MAM
This is quite similar to how you'd store the data in a relational database. After all: rows are rows, no matter what tabular structure you store them in.
If courses could be nested, you'd add a ParentID column to hold the reference to the parent course.