Requests for a PODS API

[staude]

As discussed with Phil in the slack in the #dev-chat channel, I describe what we do with PODS and what our requirements for an API would be.

We use PODS on our website https://material.rpi-virtuell.de

rpi-virtuell was developed as a virtual religious education institute on the Internet. It provides a wide range of practical help, teaching media, as well as central learning- and communication-technologies and supports teachers in the various areas of religious education in schools and churches.

The "Materialpool" of rpi-virtuell is a constantly growing digital media library for religious education professionals. Almost all content is public and free of charge. Openly licensed materials (OER) can be easily adapted to one's own practice and provided with own tasks.

Each material is checked for content, indexed and sorted by topic. Furthermore, our visitors can evaluate previously recorded materials and add critical constructive comments to them.

For this purpose, we have developed an extensive input interface in which our employees edit the entries.

In the following I describe the special features, which we built with JS.

After calling up the input interface for a new entry, the language and availability are automatically filled in. This is not a pods default value, but can have different default values depending on the employee.

We also have a dependency between education stage and age.

Clicking on an education stage automatically selects the superior education stage and the corresponding age groups are also selected. For example, if I just click on "Work with children", the system automatically checks "Community" in the education level and the entries "05-10" and "10-13" of the age group are also automatically checked as well.

Our most important feature is also the most unimpressive. Our keywords.

For example, if I enter "Adventszeit" as a keyword

will automatically change to "Advent" after you type it in.

The mechanism for this is as follows. If a keyword is entered, we check. a: is the keyword in our own keyword taxonomy - if yes, everything is fine, the keyword is taken over like it is.

b: If the keyword is not a known keyword, then we check if it is in our synonym database, and if yes, the so called standard word / "Normwort" is taken from the synonym database as a keyword into the field.

c: if the keyword entered is not known to us as a synonym, we will ask the web service of a library. This web service returns us the standard word and all synonyms. The synonyms are stored in our synonym database and the standard word is stored as a keyword in the keyword table and used as a keyword in the mask.

d: even if the library service does not know the keyword, the user gets a hint that he has to investigate himself.

This results in the following requests for an API

Reading a value Writing a value Changing a value Notification (CallBack) on

• Adding a value
• Deleting a value
• Changing a value

[joerglohrer]

i know this is extensive but support would be very much appreciated

[quasel]

Hi, sounds impressive - did you discuss your needs with @pglewis any further? Your post reads a bit more about what you have done but not what do you need ;) Pods is Open Source so the Team depends on contributions and help from others ( friends.pods.io ) but maybe some of the work you haven done can be repurposed or integrated int pods?

P.S: Hallo aus Wien ;)