TOD 2024 Roadmap:1.0

[todhamma]

TOD 2024 Roadmap

• Checked tasks are ready, unchecked are in progress or planned. Classification is done in serial order.
• Please feel free to add an issue, comment, request more info, or ask for clarification.

Data (in N/W drive)

1. Naming Standard

Add what is the final naming standard decided here!

• Image
• Letter
• Audio
• Video
• Transcript
• Document
• Magazine
• Printed Book
• Diaries
• Newsletter
• Newpaper
• Painting

2. Data Sort

Note: Final Folder Structure - to be given by Amar soon.

• Raw
• Processing (Project files. Eg: Premiere Pro, After Effects, Photoshop, Audition files)
• Final
• Variations (Versions for Social media, Mega Events, etc.)
• Checked for Duplicacy?

Archipelago

3. Installation and Configurations Setup

• Step by Step way to setup domain #19

4. Webform

Webform fields according to the type of resource.

• Image
• Letter
• Audio
• Video
• Document
• Transcript
• Printed Book
• Diaries
• Magazine
• Newsletter
• Newpaper
• Painting

5. AMI Sets

• Create AMI Set acc. to the field's machine name and sort it acc. to page details (Eg: General info fields in sequence, or images/letters field in sequence, or any other way that suits the metadata admin)
• Freeze this AMI set template.

6. Roles

Define roles as to who can access what content, and which fields of the same.

• Find and list out the exact use-case as in what access has to be given to whom, when, and how? and according to add those accessibility feature details here and create role and give permissions accordingly.

Roles such as:

• a. Admin – Has full access + permissions
• b. Metadata Admin – Has full access to metadata field i.e. all content access, manage display, manage form display, webform access, comments section, display suite, metadata display (twig template), facets, Search API - esmero-solr search, manage AMI sets
• c. Metadata API – Has access to manage content, manage display, manage form display, upload content, edit content, manage AMI sets
• d. Digitizer – Metadata API + Digitization group is added.
• e. Conservator – Metadata API + Conservation group.
• f. Teacher -
• g. OS -
• h. User -

7. Metadata & Twig Template (Look and feel) - Everything related to it

• Edit metadata (content) display – to limit the fields to be seen by the user – ismemberof, ispartof, title, author(s), date published, files link to download, rights statements.
• Similarly, restrict content display view for other roles.

Q/A:

• Do we require one webform OR multiple webforms for our use case?
  Ans: For this, multisite is better. How to implement multisite?
  Solution: Codebase will be the same for all sites.
  a. Create a new directory in sites/ as the URL name for the site. Eg: giri.vridhamma.org for DhammaGiri.
  b. Add settings.php in each site folder and add a new DB name in the config engine.

Note: If you have say 100 sites and each site is pointing to a separate DB with the same codebase, then any update in drupal say will affect all 100 sites. Eg: Curren Dana's site - handling 60 centers - has the same codebase with different sites folder.

• How to maintain multisite features for centers?
  Solution: Create a central site. The DB of this site is the central DB.

Expose API from this site to all center's sites. Solved! API is powerful.

• To Create a proper AMI set of folders (collections) with all metadata, do we carry this out at once (100% fields filled) OR fill only General info + Files upload (via s3 minio)
  Ans: First import for each category should be with complete metadata, then with a few details refining web-form fields, etc., and freezing folder structures and any update that is required.

• Do we upload 1 subfolder each from a directory of all N/W drives OR start by uploading all data from an entire N/W drive and carry on with the remaining N/W drives?
  Ans: Extending above answer - first batch is 1 subfolder from each drive(category), then push entire drive at once.