Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Array of bylines CR 10-29 #29

Open
jolla56 opened this issue Aug 28, 2019 · 3 comments
Open

Array of bylines CR 10-29 #29

jolla56 opened this issue Aug 28, 2019 · 3 comments
Labels
investigation To be further investigated and discussed.

Comments

@jolla56
Copy link
Contributor

jolla56 commented Aug 28, 2019

New property “bylines”:

"bylines": {
            "description": "Holder of one or more byline objects.",
            "type": "array",
            "items": {
                "type": "object",
                "properties": {
                    "byline": {
                        "type": "string",
                        "description": "When the complete byline is sent as one string. Same as byline on root level. Example: Albert Jonsson/SvD/TT"
                    },
                    "firstname": {
                        "type": "string",
                        "description": "When byline is divided, holds the first name of the person. Example: Albert"
                    },
                    "lastname": {
                        "type": "string",
                        "description": "When byline is divided, holds the last name of the person. Example: Jonsson"
                    },
                    "role": {
                        "type": "string",
                        "description": "Role of the person in the byline in relation to this ttninjs item, as string. Example: Photographer"
                    },
                    "email": {
                        "type": "string",
                        "description": "Email address of the person in this byline. albert.jonsson@acme.com"
                    },
                    "jobtitle": {
                        "type": "string",
                        "description": "Jobtitle can differ from role and is normally more connected to the person and not to the combination person-newsItem. Example: Editor in Chief"
                    },
                    "internal": {
                        "type": "boolean",
                        "description": "Whether byline is for internal purposes. Example: true"
                    },
                    "phone": {
                        "type": "string",
                        "description": "Phone number of the person in this byline. Example: +46555123456"
                    },
                    "initials": {
                        "type": "string",
                        "description": "Initials of byline. Mainly used for records marked as internal. Example: mag"
                    },
                    "affiliation": {
                        "type": "string",
                        "description": "The affiliation of the person. Example: SvD/TT"
                    }
                }
            }
        },

Rationale for the change: (free-text)

The present byline property is a string that we use for the publishable byline. This suggested construction is for adding all contributors to the item. And giving them a role etc.

See also http://dev.iptc.org/ninjs-CR-10-10-contributors.

@jolla56 jolla56 closed this as completed Sep 11, 2019
@jolla56 jolla56 reopened this Sep 11, 2019
@bquinn
Copy link
Contributor

bquinn commented Sep 11, 2019

So the idea is that people could use either the single-string byline or this rich bylines property? What would the semantics be if people used both?

@jolla56
Copy link
Contributor Author

jolla56 commented Sep 12, 2019

I think the byline property as a string is for publishing. It can hold more than one name. But no structure. So what's there is usable as is.
If you like to provide a structured array of bylines of people involved you can do this here. But it can be photographers in wich case you might want to handle that separately from authors etc. So I don't see a problem with using both.

@jolla56
Copy link
Contributor Author

jolla56 commented Sep 12, 2019

Compare with contributors: #10

@jolla56 jolla56 added the investigation To be further investigated and discussed. label Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigation To be further investigated and discussed.
Projects
None yet
Development

No branches or pull requests

2 participants