codespilot / vocadb Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/vocadb
Automatically exported from code.google.com/p/vocadb
It should be possible to merge all types of entries (artists, albums, songs).
When an entry is merged, the source entry is deleted and all links are updated
to the target entry. Many-to-one properties like web links and names are also
merged, but singular properties such as artist type, are not.
Merging should probably be a separate permission type, but it might be granted
to new users by default.
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 8:07
Have lists open to the community, like lists for the vocaran, utaran, and
utauran.
Original issue reported on code.google.com by [email protected]
on 1 Nov 2011 at 2:44
Small 25x25 - 50x50 px icons?
Original issue reported on code.google.com by [email protected]
on 1 Nov 2011 at 2:53
Expand the current "my collection" feature by allowing wishlisted and ordered
albums
Original issue reported on code.google.com by [email protected]
on 15 Jan 2012 at 1:12
I can't enter my account, My user name is Flower Metal
Original issue reported on code.google.com by [email protected]
on 2 Nov 2011 at 5:17
Use current yellow information box as a template for general notifications and
private messages.
Site state notification: is displayed only on front page (Home) to everyone.
Global notification: acts as a private message to everyone (see private
message). Can be used to inform users about upcoming downtime.
Private message: is showed to a certain logged user on EVERY page until he
clicks [x] (closes it). Can be used by mods to ask user to change activity
(delete a duplicate, stop adding new, stop spam etc) or to say that he's
awesome. Users can't send private messages other to users except a special user
that exists for feedback (discuss). Mods can send pm's to anyone.
Original issue reported on code.google.com by [email protected]
on 2 Nov 2011 at 3:12
For example "All Night Leleledio!"
Original issue reported on code.google.com by [email protected]
on 28 Oct 2011 at 6:54
There should be groups for at least:
- Limited users (cannot actually edit the database)
- Regular users
- Trusted users (can delete and merge entries)
- Moderators (can disable accounts and delete comments, most likely see the
audit log, can manage trusted users)
- Administrators (can access the admin tasks and manage all users)
- MikuDB importer (special group for importing albums from MikuDB)
User should still be able to belong to any number of groups, although most of
these groups are hierarchial (Admin permission supersedes Moderator which
supersedes Trusted users in turn).
Original issue reported on code.google.com by [email protected]
on 28 Nov 2011 at 1:08
Two revisions of any entry can be selected for comparison in the same view.
By default the system should suggest the previous version to the selected
version, because that' the most common use case (to see which properties
changed).
Original issue reported on code.google.com by [email protected]
on 2 Dec 2011 at 7:35
Like artist's albums and songs: display the most popular results of a tag on
the overview page and the rest in other tabs.
Original issue reported on code.google.com by [email protected]
on 18 Dec 2011 at 10:58
Currently they're always in default language.
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 12:42
Every entry may have a short note
Original issue reported on code.google.com by [email protected]
on 30 Jan 2012 at 10:46
Like on Mikubook, but I believe we can do it better
Original issue reported on code.google.com by [email protected]
on 6 Dec 2011 at 4:20
Currently all changes are logged and old versions are archived, but there is no
possibility to restore those old versions. Moderators should be able to inspect
which changes have been made and restore old versions if needed. Likewise
moderators should be able to restore deleted entries.
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 8:29
Currently the original picture is used as-is. For many views the original
picture is much larger than necessary and bandwidth could be saved by serving a
smaller picture instead. The code already supports images of multiple sizes,
but this has not been implemented to image uploads yet.
Original issue reported on code.google.com by [email protected]
on 19 Oct 2011 at 6:55
it shouldn't matter whether the search includes the "P" or "-P" suffix.
Original issue reported on code.google.com by [email protected]
on 21 Oct 2011 at 11:28
Something better than the current one
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 12:42
Currently no UI for this
Original issue reported on code.google.com by [email protected]
on 25 Feb 2012 at 10:22
Add links to log, for example:
"adding song 'My fxxkin desire for you' [1623] to album 'Vocarock - Hope' [223]"
-->
"adding song 'My fxxkin desire for you' <a
href="http://vocadb.net/Song/Details/1623">[1623]</a> to album 'Vocarock -
Hope' <a href="http://vocadb.net/Album/Details/223">[223]</a>"
Original issue reported on code.google.com by [email protected]
on 2 Nov 2011 at 1:58
To help new fan base members, have a list of highly ranked songs.
Original issue reported on code.google.com by [email protected]
on 1 Nov 2011 at 2:41
Archived versions should be saved as diffs. This would save a large amount of
space. Possibly there could be snapshot versions, for example between specific
version numbers or dates. Diffs would also make it possible to compare entries
together, which would be useful in many ways.
Original issue reported on code.google.com by [email protected]
on 10 Nov 2011 at 11:14
Currently the login is using a temporary cookie which is deleted when the
browser window is closed. That causes the user to be logged out. Either the
session timeout needs to be made longer or some other automatic login based on
a cookie could be implemented.
Original issue reported on code.google.com by [email protected]
on 15 Jan 2012 at 1:28
Allow adding artist links to multiple tracks at once based on artists linked to
the album.
Original issue reported on code.google.com by [email protected]
on 21 Oct 2011 at 11:27
Existing and future entries should be importable from mikudb.com. At least
album names, artists, release year and tracklists should be imported. Imported
albums include a link back to mikudb.com.
Mikudb.com doesn't use consistent naming for artists, so missing artists will
be skipped. Missing albums and songs will be created. If the album already has
at least one track, tracklist for that album will not be imported. Artist lists
will be merged.
New albums will be added to a specific list where they can be inspected before
accepting them to VocaDB.
MikuDB import is a specific permission.
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 8:23
replace "Add an artist", "Submit an album" and "Submit a song" with icon,
button or text like [add] on the same line, for example:
Artists [add]
Albums [add]
Songs [add]
Original issue reported on code.google.com by [email protected]
on 2 Nov 2011 at 1:55
The same feature could possibly be available to all users, so that anyone could
anyone else's contributions. This might need a privacy setting though.
Original issue reported on code.google.com by [email protected]
on 2 Dec 2011 at 9:29
Might consider allowing the deletion of empty tags only.
Original issue reported on code.google.com by [email protected]
on 26 Jan 2012 at 9:44
Currently the notification stays on the top of the page until the user reads
the message. Either the notification should be made more subtle, or it should
be possible to dismiss messages without reading them.
Original issue reported on code.google.com by [email protected]
on 22 Nov 2011 at 8:33
Currently, there's only user activity, that may make users feel uncomfortable
by being constantly watched and displayed.
Request: *add* new *finished* entries roll to front page, for example, albums
with thumbnails of their cover with short info. Could look nicely.
Original issue reported on code.google.com by [email protected]
on 24 Mar 2012 at 11:47
For producers/live singers: the date they started making Vocaloid music.
For Vocaloids: release date.
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 12:38
Songs could really use a few extended attributes. Some of these could be
implemented with tags as well.
For example:
- Performance language (free-form or premade list)
- Other responsible people besides the main artists (lyricists, guest
performers etc.) (most likely free-form)
- Beats-per-minute (bpm) (free-form, but numeric)
Original issue reported on code.google.com by [email protected]
on 5 Dec 2011 at 5:24
Currently the search box is just a textbox + a list under it. The search
results list could be enhanced in multiple ways: if using something else
besides a listbox, the search results could contain a link to the entry. The
results should also provide more information, for example all translated names
and type of result (for example for songs, whether it's original, remix or a
cover).
Original issue reported on code.google.com by [email protected]
on 20 Nov 2011 at 10:59
Right now the only way to get info from vocadb is via the web site, it would be
awesome if a API was implemented so this info can be accessed from other
applications like music players, desktop search, smarthphones, etc. The API
should be limited to a number of queries in a range of time to prevent abuse
and server strain.
The api directory could be of the following structure:
(The extension could be xml too so one can choose the data format)
/api/artist.json
/api/album.json
/api/song.json
/api/tags.json
or a merged one like:
/api/entry.json
So one can use a parameter to get the corresponding query.
Note: All the api calls must have the accessKey attached.
API description:
Songs:
Base url: /api/song.json | /api/song.xml
* id: identifier of the song to search for
* name: name of the song to search for
* name_pattern: search for any song that has this parameter in its name
* language: one of 'English | Romanized | Non-english | Unspecified'
* limit: how many songs to retrieve
* before_id: only return results with id before this one
* draft: set it to True to include draft entries in the results
Tags:
Base url: /api/tags.json | /api/tags.xml
* id: identifier of the tag to search for
* name: name of the tag to search for
* restrict: one of 'artist | song | album'
* limit: max number of matches to return
* before_id: only return results with id before this one
* draft: set it to True to include draft entries in the results
Album:
Base url: /api/album.json | /api/album.xml
* id: identifier of the album to search
* catalog: search the album by the catalog number (e.g. MHCL-2015)
* name: name of the album to search
* name_pattern: search for any album that has this parameter in its name
* artist_id: search for albums from this artist
* language: one of 'English | Romanized | Non-english | Unspecified'
* record_type: one of 'Compilation | Album | Single | EP | Other'
* limit: max number of results to return
* before_id: only return results with id before this one
* draft: set it to True to include draft entries in the results
Artist:
Base url: /api/artist.json | /api/artist.xml
* id: identifier of the artist to search
* name: name of the artist to search
* name_pattern: search for any producer that has this parameter in its name
* language: one of 'English | Romanized | Non-english | Unspecified'
* type: one of 'Producer | Circle | Label | Vocaloid | UTAUloid | Other'
* limit: max number of results to return
* before_id: only return results with id before this one
* draft: set it to True to include draft entries in the results
Original issue reported on code.google.com by [email protected]
on 9 Feb 2012 at 4:58
From issue 12:
Three status levels will be added for now: Draft, Finalized and Locked.
Entries may start out as Draft or Finalized. Draft status is indicated on the
entry details page. Any registered user can change the status from Draft to
Finalized, provided that certain conditions have been met. For example albums
need at least one artist and a type that isn't "unspecified". Might add the
requirement for a tracklist as well. Privileged (trusted) users may change the
status back to Draft.
Privileged users may lock any entry that is Finalized. Locked status is
indicated on the entry details page. Locked entries can still be edited by
these privileged users, but not others. Privileged users may unlock an entry,
changing its status back to Finalized or Draft.
Status information needs to be added to revisions as well, so that users may
see when the status of the entry changed.
Need to decide whether changing the status requires a new revision. This
probably isn't necessary. Also, need to decide whether changing the status can
be done from the edit page, revisions page, or both.
Original issue reported on code.google.com by [email protected]
on 27 Nov 2011 at 7:26
Support searching of albums by release event (Komiket/VoMas)
Original issue reported on code.google.com by [email protected]
on 24 Mar 2012 at 11:41
If user searches for an entry and there's a single result with high similarity
% with search string contents, navigate directly to that entry.
Most of time, users are searching for certain single entries.
Original issue reported on code.google.com by [email protected]
on 24 Mar 2012 at 11:44
Not saved
Original issue reported on code.google.com by [email protected]
on 16 Feb 2012 at 12:10
Counts as "favoriting" that artist. There should also be a special
user-specific feed that displays activity related to that user's followed
artists.
Original issue reported on code.google.com by [email protected]
on 13 Feb 2012 at 12:47
A role can be specified for artists that are involved with any album or song.
This would allow adding of illustrators, lyricists, composers, arrangers,
performers etc. Some open questions remain though. In practice groups/labels
and vocalists already specify a role and with very few exceptions can't act in
different roles. Not sure if the role selection should be limited to only
certain artist types (basically producer and "other individual"/support). The
same person can also act in multiple roles (lyricist, composer, performer).
Original issue reported on code.google.com by [email protected]
on 8 Feb 2012 at 10:49
The default description could be read from the video service, but the user
should be able to edit it.
Original issue reported on code.google.com by [email protected]
on 6 Dec 2011 at 10:17
Need a many-to-many association instead of one-to-many
Original issue reported on code.google.com by [email protected]
on 18 Oct 2011 at 12:41
So covers and remixes can be easily discovered.
Original issue reported on code.google.com by [email protected]
on 1 Nov 2011 at 2:49
Preset choices: invalid information, missing information, broken PV etc.
Tied to user account (if logged in) or IP address, so that one user can't
report the same entry multiple times.
Original issue reported on code.google.com by [email protected]
on 27 Feb 2012 at 4:35
Currently, users can create duplicate producer entries without even being
warned.
Check and warn (confirm?) user about creating duplicate producer entry.
Original issue reported on code.google.com by [email protected]
on 2 Nov 2011 at 4:20
Even if the site structure isn't very complex, a sitemap would be useful (for
search engine optimization as well).
Original issue reported on code.google.com by [email protected]
on 29 Nov 2011 at 10:59
At least draft/stub status should be allowed, maybe others.
Original issue reported on code.google.com by [email protected]
on 29 Oct 2011 at 10:42
The same view as for changing the media type.
Original issue reported on code.google.com by [email protected]
on 21 Feb 2012 at 2:06
Especially for those events that may take a while, such as adding a new PV.
User should also get a notification for the completion of an AJAX event, for
example adding a song to a list.
Original issue reported on code.google.com by [email protected]
on 25 Feb 2012 at 9:22
General information about the site, about Vocaloid and how to contribute
(create and edit entries).
Original issue reported on code.google.com by [email protected]
on 31 Oct 2011 at 11:18
Currently, album lists of artists are sorted by order of adding to db and don't
contain useful information like release dates or thumbnails of covers, which
makes user to open each album to see cover/date and get an idea what it is.
Request: add at least cover thumb and release date (and sort by it) to album
lists, like "All albums" tab in Artist' entries.
Original issue reported on code.google.com by [email protected]
on 24 Mar 2012 at 11:50
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.