Skip to content

ARD Solid Pod Structure

Adrian Vega edited this page May 1, 2023 · 2 revisions

Solid Pod Structure

Problem

Need an structure that allows us to retrieve, add and delete information from the pod in the best possible way. The architecture followed in the directories of the pod is the following:

  • General folder -> .../private/lomap/
  • Inventory folder -> .../private/lomap/inventory: contains a record of all the stored locations of the user.
  • Locations folder -> .../private/lomap/locations: contains subdirectories (one for each location stored) storing all the location data.
  • Locations images -> .../private/lomap/locations/locationId/images : Stores the images of the location.

Advantages

  • If we store the locations following that structure we can keep in the same place all the information regarding a particular location, which allows us to have a better organized pod architecture and favors the sharing of locations with the user's friends.
  • Each location folder will be translated in a Solid Dataset, which eases not only storing "lists" of objects, such as the reviews, images or ratings of the locations, but also to grant access to determined objects to determined people.

Alternatives

One of the possible alternatives of the directory structure in the pod was to have:

  • One folder containing the locations -> .../private/lomap/locations
  • One folder containing subfolders containing the images of each location -> .../private/lomap/images
  • One folder containing subfolders containing the reviews of each location -> .../private/lomap/reviews
  • One folder containing subfolders containing the ratings of each location -> .../private/lomap/ratings This was not effective, since it difficulties scalability and does not follow the idea of having all the information regarding one location in the same place.