Shiroizu

Results 35 issues of Shiroizu

New API endpoint for tracking when tags get added (or removed) to/from entries. This would allow more efficient moderation work. https://vocadb.net/api/activityEntries?userId=329 https://vocadb.net/api/comments?userId=329 https://vocadb.net/api/taggings?userId=329 {NEW} ### Checklist (required) Fill out the...

priority: low
content: tags
moderation
API
complexity: unknown
feature request

Related issues: - https://github.com/VocaDB/vocadb/issues/1953 - https://github.com/VocaDB/vocadb/issues/1954 The visibility of the video player / bottom bar should be toggleable without clearing the [playlist](https://vocadb.net/playlist). The video playback should stop when hidden. The...

priority: low
UX/usability
content: song lists
complexity: medium
media
feature request

This would help with the entry editing flow, as the player can take a lot of space on smaller screens.

priority: low
UX/usability
content: song lists
media
frontend
adding/editing entries
complexity: unknown
feature request

The bottom bar should be hidden if the [playlist](https://vocadb.net/playlist) is empty. ![Image](https://github.com/user-attachments/assets/4f66e47a-84d0-48e3-942e-b42bee5fbb41)

priority: low
UX/usability
content: song lists
complexity: low
media
frontend
UI
feature request

Relevant rule: https://wiki.vocadb.net/docs/pinned/rule-reference#rule-matching-artist-collaboration-role-and-tag > Tag the artist with the secondary artist types when appropriate. > For example, if an `Animation producer` (artist type) is responsible for the lyrics (as a...

priority: low
content: tags
complexity: low
content: artists
frontend
feature request

Currently there is significant data duplication between artist/album and song entry taggings. This could be solved by automatically calculating the most relevant tags for each artist and album entry based...

priority: low
content: tags
content: songs
complexity: high
content: albums
content: artists
feedback-wanted
backend
feature request

Add release field for albums, instead of relying on tags https://vocadb.net/T/93/digital-only ![Image](https://github.com/user-attachments/assets/286a4b71-0b27-406c-a7b0-7ed8c15ba9cd) Would additional release options be necessary?

priority: low
content: albums
feedback-wanted
complexity: unknown
feature request

Transferred from https://code.google.com/archive/p/vocadb/issues/113

priority: low
UX/usability
content: song lists
complexity: high
content: users
content: albums
content: artists
feature request

Transferred from https://code.google.com/archive/p/vocadb/issues/89

priority: low
moderation
images
complexity: unknown
feature request

The /api/releaseEvents could return the relevant (album/artist/song) entry counts when a field for it (`entryCounts` for example) is specified. https://vocadb.net/api/releaseEvents?maxResults=1&fields=entryCounts Example output: ```json "category": "Contest", "date": "2023-09-01T00:00:00Z", "endDate": "2023-10-30T00:00:00Z", "id":...

priority: low
content: search
content: events
API
complexity: high
frontend
backend
feature request
external solution possible