-
## Description
There is a one-to-many relationship between `Organization` and `Metadata`. We have two approaches to model this relationship.
### Linked (Denormalized) Data
```
{
"id": "",
"nam…
-
## Description
The current CCX ``CustomCourseForEdX`` model in Open edX does not include a flexible field that allows users to store custom metadata or other types of additional information. This l…
-
## Error
```
Error:
0: Planner error
1: Error executing action
2: Action `encrypt_apfs_volume` errored
3: The keychain lacks a password for the already existing "Nix Store" volume o…
-
**Describe the bug**
We want to store additional metadata to a Step (e.g. current RAG context or document infos). We want later to reconstruct a Thread with such extra info.
Such metadata is store…
-
**Acceptance Criteria**
- [ ] Add a new metadata field, Condition, to be stored for any new saved template
- [ ] Condition field is an open text field
-
Many data dictionaries are simple flat tables of field names and definitions. However, some have more complex schemas where certain fields have their own codebooks.
Here is an example: https://resour…
-
- [ ] Separate edm::IndexIntoFile into a stored component and a runtime component
- [ ] Separate edm::ProductRegistry into a stored component and a runtime component
-
The config override:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: rook-config-override
namespace: rook-ceph
data:
config: |
[global]
rgw_enable_static_website = true
…
-
I am planning to refactor the [existing Embeddings class](https://github.com/holoviz/lumen/blob/main/lumen/ai/embeddings.py#L6).
The purpose is to supply LLMs with up-to-date or private data using re…
-
_Original title: Perhaps metadata should all live in a `_metadata` in-memory database_
Inspired by #1150 - metadata should be exposed as an API, and for large Datasette instances that API may need …