8564_w not present in data model

[jacquerie]

From @jmartinm on August 11, 2016 7:37

The data model in inspirehep.net for URLs looks like:

And the new data model has value and description:

"properties": {
        "description": {
            "type": "string"
        },
        "value": {
            "format": "url",
            "type": "string"
        }
    }

While implementing the journals detailed view I have seen that we are missing some information that is contained in 8564_w and used to describe what volume the URL corresponds to:

https://inspirehep.net/record/1214516

Would it be enough to use the description field for this? Or we think we need a new field?

Copied from original issue: inspirehep/inspire-next#1430

[jacquerie]

From @kaplun on August 11, 2016 7:59

@inspirehep/inspire-content what is the meaning of 8564 $w indeed? Many records have it but is not used in formats and I doubt it is searched. How is it populated?

[jacquerie]

From @kaplun on August 11, 2016 8:0

For reference this is connected with #463

[jacquerie]

From @ksachs on August 11, 2016 8:37

this goes back to SPIRES where we had 2 pieces for a URL: the base-part as a lookup-table/knowledgebase ($$y)+ the specific piece for this paper ($$w) This made it easier to move the URLs in case the server changed.

e.g. $$y:JACOW -> http://accelconf.web.cern.ch/AccelConf/ + $$w:p91/PDF/PAC1991_1461.PDF

http://accelconf.web.cern.ch/AccelConf/p91/PDF/PAC1991_1461.PDF

30751 8564_ $$uhttp://accelconf.web.cern.ch/AccelConf/p91/PDF/PAC1991_1461.PDF$$wp91/PDF/PAC1991_1461.PDF$$yJACOW

[jacquerie]

From @kaplun on August 11, 2016 9:36

Oooh. Interesting. Isn't this then superseded nowadays by careful usage of 035, where we just store the external ID, and we are then able to link to the splash page of the document? Because in principle also the $w value in your example could be subject to changes by the external service.

I see also that the URL in $y is anyway the full one, so $w contains just the suffix. So in principle we can ignore it during the migration, and in case move those URLs to use the 035 technique.

[jacquerie]

From @hoc3426 on August 11, 2016 14:49

Yes, 035 and 0247 (DOI) have largely done away with any need for this.

[jacquerie]

From @annetteholtkamp on August 18, 2016 14:59

Anyway, all these have been expanded into a complete url when migrating from Spires to Inspire. This subfield has never been used in Inspire as far as I’m aware.

• Annette

On 11 Aug 2016, at 14:49, hoc3426 notifications@github.com wrote:

Yes, 035 and 0247 (DOI) have largely done away with any need for this.

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/inspirehep/inspire-next/issues/1430#issuecomment-239184335, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1-Oz8EIvaKPN9NRh_aMpuvyw_0XWDjks5qezZmgaJpZM4Jh3cB.

[jacquerie]

From @kaplun on September 30, 2016 15:16

@inspirehep/inspire-content I realize now that this specific issue @jmartinm raised was related to journal database. What shall we do with 8564_$w in that case?

[jacquerie]

From @hoc3426 on October 12, 2016 17:18

These can be handy, if, say, you want to show everything that is linked to "symmetry" magazine, but we probably contain the necessary information in the $y field now.

On Fri, Sep 30, 2016 at 10:16 AM, Samuele Kaplun notifications@github.com wrote:

@inspirehep/inspire-content https://github.com/orgs/inspirehep/teams/inspire-content I realize now that this specific issue @jmartinm https://github.com/jmartinm raised was related to journal database. What shall we do with 8564_$w in that case?

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/inspirehep/inspire-next/issues/1430#issuecomment-250771568, or mute the thread https://github.com/notifications/unsubscribe-auth/AIkYYECG50YoQtgK3EwbOqOPfieLFBKrks5qvSfOgaJpZM4Jh3cB .

[jacquerie]

From @annetteholtkamp on October 13, 2016 14:28

There are only 9 journal records affected. Either it says Open Access - this info should definitely go somewhere else. http://journals.aps.org/prab/ http://journals.aps.org/prab/ (Open Access) Or it specifies in case of subseries A,B… to which subseries a url belongs. .
Physical Review  https://inspirehep.net/record/1214516 Phys.Rev. http://pra.aps.org http://pra.aps.org/ (A) http://prb.aps.org http://prb.aps.org/ (B) http://prc.aps.org http://prc.aps.org/ (C) http://prd.aps.org http://prd.aps.org/ (D) http://pre.aps.org http://pre.aps.org/ (E)

Since we intend to create separate records for the subseries these url’s just have to be added to the right records. Then this subfield becomes obsolete.

• Annette

On 30 Sep 2016, at 15:16, Samuele Kaplun notifications@github.com wrote:

@inspirehep/inspire-content https://github.com/orgs/inspirehep/teams/inspire-content I realize now that this specific issue @jmartinm https://github.com/jmartinm raised was related to journal database. What shall we do with 8564_$w in that case?

— You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub https://github.com/inspirehep/inspire-next/issues/1430#issuecomment-250771568, or mute the thread https://github.com/notifications/unsubscribe-auth/AM1-O8dW6v3MoEbdulCjB6FhlkfSOFzdks5qvSfOgaJpZM4Jh3cB.

[jacquerie]

Data model decision, so something for @michamos to decide.

[michamos]

As @annetteholtkamp said, this doesn't seem needed now that we are splitting journals.