Open ben3000 opened 2 months ago
@ben3000 So, we wont be recording any publications data from that API on our db, since it would be duplication and editing is handled by the library, correct?
Is that table there to show what fields we will be using from the api? Could you please provide the ordering of the fields as it would be displayed on the frontend - e.g. like a reference?
publication_string = `${BilboAuthor}, ${BilboTitle} ${BilboVolume}, ${BilboPages}`
I can add employee_id to the sections where I added it_asset_id to ensure that we can link up to the library system and call their api with that number.
But in order to do that, please also send me their api link/s and system credentials to access them (for example, IT assets required an email (bcs@dbca.wa.gov.au) and token, which were used with Basic Auth)
@idabblewith Correct, no recording/storing of publications, unless it becomes obvious that we need to store them in a cache for performance reasons. I'll pop in the formatting algorithm shortly.
@idabblewith I've given you access to the old Science Internet webapp repo so I can point you to the Bibliography formats it handles:
Profiles should contain publications derived from two sources:
employee_id
in IT Assets is the unique ID of authors in the Library system.