Allow non-unique (duplicate) property values in a list

Feature archive
,
1

Use case or problem

I am documenting a media archive and assign one note per recording. In the note, I am identifying individual media clips from within the recording, and assigning respective dates, durations, and start and end times. When a given clip takes place on the same date as another clip, I would like to be able to assign the same date value for that clip. Unfortunately, Obsidian recognizes the non-unique value, and wants me to change the value.

Example 
dates:
  - 1990-08-26
  - 1990-08-27
  - 1990-08-31
  - 1990-09-02
  - 1990-09-04
  - 1990-09-04
  - 1990-09-05
  - 1990-09-05
clip-start-times:
  - 00:00:00.000
  - 00:26:34.876
  - 00:34:01.005
  - 00:44:31.770
  - 01:25:10.026
  - 01:33:50.443
  - 02:00:57.334
  - 02:04:31.974
clip-end-times:
  - 00:26:34.876
  - 00:34:01.005
  - 00:44:31.770
  - 01:25:10.026
  - 01:33:50.443
  - 02:00:57.334
  - 02:04:31.974
  - 02:04:50.283

Proposed solution

Permit non-unique values in a list property type.

Current workarounds

  1. Include times in the date values (unfortunately, I do not have time info for the majority of the media clips)
  2. Prepend/append arbitrary characters or other values to the values (breaks the date, looks strange)
  3. Scrap the one-note-per recording idea and use a one-note-per-clip system instead (clashes with how I would prefer to organize my data, creates more work)
4 Likes
3

thanks for creating the FR.

4

My pleasure, it was my first. :smiley:

Regarding the FR, I’m currently not entirely sure I understand what I’m seeing, as I’ve come to notice, since posting the above, that Obsidian does actually permit non-unique values, but only when I enter them in Edit mode. So I think the issue summary and description may need to be updated, as soon as I and or/we determine what the expected behavior actually is and what’s going wrong.

5

Got the same problem for trying to count reps in a set when using properties for keeping track of workouts. Thought it would be cool to combine it with bases and templates to do some data analysis of some kind.

Also interesting to note that you can force this by going into source mode as this is not a restriction of YAML itself, but by Obsidians own restrictions.

6

will be implemented in v1.10. No ETAs.

7

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.