ePocs Collection
Guide to describing and structuring an ePocs collection for import into the ePoc mobile app.
Collection Metadata
A collection is defined by the following information:
- id: Unique identifier (e.g., 
fr.inria.learninglab.epocs). - title: Title of the collection (e.g., "ePoc Collection - Inria Learning Lab").
 - description: Description of the content or purpose of the collection.
 - publisher: Entity responsible for publishing (see the "Publisher" section in the "Data Format" page).
 - licence (optional): Default license for the collection (see the "License" section in the "Data Format" page).
 - url: URL to retrieve the collection (e.g., 
https://example.com/epocs/collection.json). - tags (optional): Keywords for categorization (e.g., "education", "mobile").
 - ePocs: List of included ePocs, with each ePoc identified by a unique ID and its metadata.
 
Example JSON Structure
Below is an example JSON file describing an excerpt from the Inria Learning Lab ePoc collection:
Adding to the Mobile App
To import an ePoc collection into the mobile library:
- Host the JSON File: Place the collection's JSON file on an accessible server (e.g., GitHub or GitLab Pages).
 - Import the Collection: See the "Adding a Collection of ePocs" section in the Import Guide.
 
Best Practices
- Use unique identifiers for each collection and ePoc.
 - Fill in all required fields for each ePoc and collection.
 - Always specify the license to avoid copyright issues.
 
If you need help creating your own collection or have any questions, feel free to contact us!