Freebase: Discussion about spencermountain

Barcode: Barcode & Catalog Number

2009-12-25T08:31:41.0013Z

Thanks Tom for this explanation.

Phil.B

Barcode: Barcode & Catalog Number

2009-12-24T23:24:13.0000Z

CVT = "compound value type"

If you're familiar with modeling in UML, it correlates to a UML Association Class. If you're not familiar with UML, it's basically a link + associated data. Rather than saying

CD --> ownedBy --> Phil

it says

CD --> ownedBy (fromDate, toDate) --> Phil.

In actual fact, at the most primitive level, it's just a set of nodes and arcs in the graph, but it's useful to think of this particular "clump" of nodes as a single object or link with attributes.

Barcode: Barcode & Catalog Number

2009-12-24T23:22:13.0006Z

CVT = "compound value type"

If you're familiar with modeling in UML, it correlates to a UML Association Class. If you're not familiar with UML, it's basically a link + associated data. Rather than saying

CD --> ownedBy --> Phil

it says

CD --> ownedBy (fromDate, toDate) --> Phil.

In actual fact, at the most primitive level, it's just a set of nodes and arcs in the graph, but it's useful to think of this particular "clump" of nodes as a single object or link with attributes.

Barcode: Barcode & Catalog Number

2009-12-24T20:46:16.0005Z

Yes Chris, I agree with you.

Nevertheless, I don't understand what a CVT means. Could you explain, please?

Your idea of ratings and review is very good but I don't know how to implement such 'personal' fields ...

Regards

Phil.B

Barcode: Barcode & Catalog Number

2009-12-24T19:16:17.0013Z

I’m not going to say whether Freebase should be used for this. I think Freebase should be used for whatever the community successfully uses it. If I were to include personal ownership, I would have a release ownership type, a CVT that correlates a person with a release and things like purchase date. Otherwise, what does it mean to see that To Venus and Back was purchased on 1999-10-20, 2002-05-30, and 2005-07-16? To see that Jane purchased it on 1999-10-20, Bill purchased it on 2002-05-30, and Joe purchased it on 2005-07-16 is arguably a little more useful. Even more useful, users could associate ratings or reviews with their ownership, as well; it would be a way to provide some access control via whatever app is creating those ownership nodes.

Barcode: Barcode & Catalog Number

2009-12-24T17:47:58.0006Z

Dear Chris,

I admit that my type 'Musical Release (Details)' is redundant. Actually this type is a kind of test and will probably be erased in a near future.

You've noticed that I've included a 'Puchases Date' field because I would like to enter individual ownership information but I realize that FreeBase may not be intended for this purpose. What would be the best way to handle this 'Purchase Date' information?

Regards

Phil.B

Barcode: Barcode & Catalog Number

2009-12-24T17:05:06.0000Z

I hadn’t noticed the Barcode type. That would be good. However, rather than linking your own Musical Release (details) to Barcode and then co-typing Musical Releases , I think it would be better to co-type Musical Releases as Barcoded Items. In general, your Musical Release (details) seems largely redundant. Original Release Date is present already. What does “Year of this Edition” gain? And “Purchase Date” confuses me; are you proposing to enter individual ownership information? The MusicBrainz ID is already present, as well, via a key, and AMG and Discogs links are best handled as keys into a namespace.

Barcode: Barcode & Catalog Number

2009-12-24T16:54:31.0013Z

Hi Crism,

and thank you very much for pointing me to the location of the catalog number. Now I understand the goal of the 'Local Release' topic.

I notice that Barcode already exist in FreeBase : http://www.freebase.com/type/schema/base/barcode/barcode This type allow to link an item (i.e. a Musical Release) to a Barcode.

Once again, many thanks for helping me on this topic.

Regards

Phil.B

Barcode: Barcode & Catalog Number

2009-12-24T14:53:19.0005Z

First, I misspoke above; we do have the catalog number, just not the barcode. Moreover, we have the date and place of Release Events. That really should be enough. See To Venus and Back for an example. I don’t believe we imported this information from MusicBrainz initially.

Barcode: Barcode & Catalog Number

2009-12-24T14:19:05.0013Z

Yes you're right, the release date could be one way to distinguish 2 releases, but the how to differentiate a UK release and a French release which should be different but released a the same date ?

I think that, as it is implemented at MusicBrainz, the only way to differentiate 2 releases is to specify BarCode, Catalog Number and even Release Date.

Regards

Phil.B