This bug was introduced on the weekend.

To reproduce, enable attributions and watch footnotes disappear. Commenting out the static function setBookMedia makes them re-appear so I would start looking in that direction first. Likely a call to get_posts is not ideal.

Description

create the jenkins build and deploy, connect with github hook

To the bare minimum functionality on the glossary add/edit term screen.

Description

In the media library interface, when adding author information, would like the ability to add multiple authors

Expected behavior:
similar to how authors are added in Book Info, would like to add multiple authors.

Actual behavior:
text field accepts one author.

Add the ability to turn on/off glossary functionality. This includes not display the tool-tip on the web view, and not display the glossary on any export format.

Only looking for images right now, also look for video and audio.

also, this function is generic enough to be a candidate for moving out of our class and be useful to other functions. look to incorporate into inc/media/namespace.php

Choose a way to display the tooltip (jQuery?), and update the short-code functionality to render the tooltip in the web display.

• Use the

  : The Description List element
  https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dl

• Displays on click
• Add class or ID to allow formatting
• Decide if supporting images/videos etc
• For all other exports, there is no link. - How this appears will be determined by the Theme Developers

some attention should be made to how the media attributions block is rendered. Would start to look in the direction of the div block media-attributions
https://github.com/pressbooks/pressbooks-book/blob/e904e14cdbbe3983d58485ba142f634c38c7e13f/assets/book/styles/components/pages/_chapters.scss

would be a PR against pressbooks-book (parent theme)

PDF/EPUB included.

Populate the media manager custom fields related to attributions by pulling the information from the Flikr API and wikemedia API. Note: Needs to be thought out more, to support multiple api's

Displayed at the end of the chapter, each attribution doesn't have to be on the same page as the image. With the title "Attributions" in a "textbox". The goal is to adhere to accessibility standards.

though it will not be relied on for use, providing some basic functionality is important.

The use case it would satisfy, is should a user not want to have a list of attributions at the end of the chapter and instead want to (and be willing to) add the id of the media item to the shortcode [media_attribution id=33] then that attribution statement (and that attribution statement only) would be generated underneath the media item. It would not need a relationship to the global theme options setting (me thinks), instead it would be similar to being able to 'override' that (like comments) if they were willing to put that shortcode in.

Pull from Glossary branch instead.

Bottom of the page, in an UL with the title "Attributions" with markup similar to what's found in a "textbox". The goal is to adhere to accessibility standards. Attributions will order themselves in the order they appear on the page.

Minimal Language:
Figure 1 "Image name" by "Author." Adapted by "Author." CC BY 4.0.

so, we want to look at adding:

• figure number field (maybe INT, maybe TEXT)
• author url (URL)

and derivative language

• adapted by field (TEXT)
• adapted by (URL)

a further requirement to adding these fields are that the must be registered meta and their input must be validated/sanitized.

At the end of the chapter.

Add another field in the media manager that allows people to demonstrate that the image is an adaptation.
These fields would go after the author fields and before the licence drow-down menu.

1. Adapted by: TEXT
2. Adapted by: URL

With the introduction of a new post type we need to ensure the import routines are capable of bringing over the data.

How do we ensure that a shortcode in the content area in the old book that was referencing a glossary term with id='99 is still referencing a glossary term that exists in the new book?

Clearly labeled, with description text letting them know where it will show up.

Using attachment_fields_to_edit Following TASL

1. Title - TEXT
2. Title Source - URL
3. Author - TEXT
4. Author Source - URL
5. License - Selectbox (Content: https://github.com/pressbooks/pressbooks/blob/dev/inc/class-licensing.php#L39)

These fields would go after the author fields and before the licence drow-down menu.

6. Adapted by: TEXT

7. Adapted by: URL

8. Figure: TEXT

Figure:
If figure field is empty, no link and no content in the caption area.

If not empty, put figure label in the caption area and link it to the attribution statement at the bottom.

Figure label at the bottom should link back to the image. (not to be confused with the html figure tag)

Edge cases?
Sentence logic?

Confirm the new content type is exposed.

new coding standards will look to an alphabetized list of functions inside a class.

functions that we introduce should be marked with @since 5.5 in the docblock

Global, default is on.

BCcampus/pressbooks-openstax-import#65

See the following for an example: https://github.com/BCcampus/pressbooks/blob/attribution/inc/admin/attachments/namespace.php#L123-L131

with the introduction of a new post type, we need to ensure that the glossary data goes with it.

https://core.trac.wordpress.org/ticket/38323

https://make.wordpress.org/core/2016/07/20/additional-register_meta-changes-in-4-6/

functions require passing tests or PR will not be accepted. Where it makes sense, we need to provide unit tests for the functions we are introducing.

use the title field of media object, no need for duplicate title field. (note: remove from register meta) Also, research the title attribute.

Follow the existing footnotes shortcode as an example to create a Glossary shortcode with 2 visual editor buttons:

Button 1:
The functionality of the Glossary shortcode will be to reference a Glossary ID, and render it in.

Button 2:
If no param list alphabetically all glossary terms that are published. Bold with a colon, followed by the definition.

Create content type called "Glossary", location and number of menu items TBD.