Structure authors information

[faloi]

To be able to do something like this in the future, authors info should be structured. My proposal is to begin with just a tag list of names (ideally with autocompletion based on previous guides) instead of the textbox, then we can adapt this in any way we want.

[faloi]

@flbulgarelli, let's continue the discussion here.

[faloi]

Furthermore, I think we should do the same with "Collaborators" field, and add an "Acknowledgment" long free text field to include everything else.

[flbulgarelli]

Ok @faloi.

So, biblioteca should hace two fields: contributors and authors. Contributors should be plain free text explaining who did which contribuition.

And authors should be an array containing

• Name
• An optional UID that allows to get the remaining information like image, city or occupation, and external link.

Regarding the UID, it is important that the editor allows to enter it from the begnining, because otherwise it will be difficult to add the information later. Unless we want to manually enter that information in a batch process.

Regarding the UID format, perhaps it could be a plain email, and get information from gravatar. Or a github username, or a linkedin id. Or support all them.

Anyway, I agree that the editor should propose you previous authors and make the process as simple and non burocratic as possible.

[faloi]

Agree with the UID, I think email would be fine: it's a simple way to contact the author and probably a PK in all the services you mentioned.

Regarding the Collaborators/Acknowledgment field, I'm not really sure if we need the former. Perhaps a simple rename could work. What do you think?

[faloi]

On second thought, my idea of Acknowledgment is more suitable for a per-chapter basis: what I want to write there is something general like "Some of the ideas of this chapter are based on the work of X, Y, and Z and also on the book B, written by W".

The problem there is guides can be included as part of many topics, and it would be difficult to decide where to display that message. On the other hand, I don't want to write it in every guide... ideas?