Link Entity type is necessary to enable lightweight 1-to-n relationship modelling

I have to create an extra entity at the moment to avoid loading expensive dependent objects.
In this case, the folder is the expensive entity and for all intents and purposes, I only need
to know for a specific issue the IDs of folders that it belongs to. Maybe there's opportunity
for improvement here.

entity Folder {
 fields {
  RecordID<Integer> RECORD_KEY;
  Parent<Folder>;
  Name<String>;
 }
}

entity FolderLink {
 fields {
  LinkID<Integer> RECORD_KEY;
  DefectID<Integer>;
  FolderID<Integer>;
  Folder<Folder>;
 }
}

entity Issue {
 fields {
  Number<Integer> ALT_RECORD_KEY;
  Project<Project>;
  LastModified<DateTime>;
  RecordID<Integer> ALT_RECORD_KEY;
  PriorityID<Integer>; /* Use ID in name here since eventually we'd want a proper object with names and ids*/
  ComponentID<Integer>;
  DispositionID<Integer>;
  TypeID<Integer>;
  Summary<String> TITLE;
  FolderLinks<Array<FolderLink>>;
 }
}