When adding a release, I find it easiest to post first the release with artist, and with that entry set in the database, then Edit relationships.
Recording Date is entered under Recording Area (leave individual artists’ relationships date for now). This is peculiar but explainable, but I do not seem able to set date only (which is often the case with historical recordings, missing area and place info) because Area is a Required field and does not have an [unknown] alternative. This seems to me due to type being Area, but then there should be an equal type Date.
It was not until this answer in another thread that I got the idea that the Recorded in Area field auto-search does not look for Places. Quoting from that thread:
So, as user I am first to set Recording Area (with Date), then Recording Place (with Date) in a field not to be found, and dito Date (to me the obvious superordinate of space:time, already from its standardized number format) only subordinate to other entities? Wrong. But clearly, from experience however newcome, all points to Recording Area being not the place to enter Recording Place? Wrong again.
Digging through Documentation, I get
https://musicbrainz.org/doc/Area & https://musicbrainz.org/doc/Place without answer,
https://musicbrainz.org/doc/How_to_Add_a_Place for places not already present in the database
(https://musicbrainz.org/doc/How_to_Add_an_Area yields Page Not Found.)
https://musicbrainz.org/doc/MusicBrainz_Database/Schema informative but not really of help here
http://musicbrainz.org/doc/How_to_Add_a_Release has a bottommost link “add the various credits” that could be more [Ctrl]+[F]-friendly as “add the various credits: How to Add Relationships
– and there you have it: Post Place MBId URL into Area field! (You get the URL by searching from outside of the Relationship Editor. For reference: [unknown] (Place)) But what happens? With Area Type ‘Recorded in’ set, the Relationship Editor resets Type to ‘Engineered in’ when pasted URL is auto-converted. Since Type field is above entity field (where URL is pasted), this is highly contra-intuitive, therefore missed, and the edit has to be corrected (Edit #42367796 in air for 6 days).
Most probably I have things upside-down, i.e. Date & Place being subordinate because they pertain to Type, Type being subordinate to higher order Relationship Area. But anyway, a user short-hand:
- When adding/editing, use 2 windows: #1 for adding/editing, #2 for searching (MBId URLs) / checking guidelines and others’ examples
- For recording place (and possibly other subordinates):
· Search Place for its MBId URL (if present in database, otherwise add it), copy it.
· Goto release (in other window), Edit relationships (right pane).
· Paste Place MBId URL into Relationship Area entity name field, wait for auto-convert to green.
· Set Type to Place, then (enter Date and) hit [Done].
· Edit, just learned: In case of mistake (such as ‘Recorded in’ reset to ‘Engineered in’ because you did not do steps in order above), an incorrect Edit needs not be cancelled/deleted/redone and queued, is better edited directly in Relationships Editor.
- Thank any lurker behind you correcting mess.
Is Recording Area the field meant for Place too? If so, would it not be better, and an easy fix, to have its search include Place too? Or is there another field for Place, then where?
Oh, and when should ‘This relationship has ended.’ be checked? I am not sure how it shows, can but guess. Search syntax “true if know ended even if do not know end date” is a good hint, but if it is meant for all cases of ended relationships (f.i. done recordings), it seems I am not alone in leaving it unchecked with reference to ‘Do not add uncertainty’ guideline.