That worked!

Thanks a lot!! It works perfectly now!
have a nice day!

Yes, Metrics is table-data.

Ahhh, matchAll=false is what I was looking for. Thank you!

if you mean the target pages for the report above? something simple like this:

{metadata-list}
|| some | field |
|| Status | this is good |
|| other | fields |
{metadata-list}

• I'm not sure if Andy changed the metadata plugin storage, but it seems to be backwards compatible with the metadata-v1 (we didn't lose any metadata during the upgrade or perform any sort of migration) and both versions of metadata are compatible with the checklist plugin, the sub-section edit plugin and the metadata-tab plugin.

• if the 'data' supply chain is fine-tuned to scaffolding, and scaffolding and metadata have diverged again on their data-store, what would it take to create a 'metadata' supply chain for the traditional metadata?

Hi Brandon,

The two macro which use References are list-data and attachment-data. List data will always use it, no matter what type of 'options' (list-option, content-options, etc) are used. The type of value returned will vary depending on the option type, of course.

report-info doesn't need it to be explicitly listed because it will automatically drill down through the returned object types until it finds a text, number or boolean value. If it gets to the bottom and it's still not one of the above, it will just call 'toString' on the object, hoping that it is smart enough to display itself. report-info also does a lot of other tricks like automatically detecting collections and iterating through them, etc., which don't make sense for filters and sorters.

This doesn't work for filters because they tend to be more specific, and automatically drilling down would provide some unexpected results in some cases.

Essentially, it is only the display macros (report-info in particular) which will automatically drill down. All other macros need to have the key chain be listed explicitly.

Ahhh, now it is working fine!

Thanks a lot for your help and your immediate response!

Günter

Thank you for the help. This would be an awesome, awesome thing. However, I couldn't get it to work properly. I had to modify it because there were some syntax stuff that was a little off, and I got some errors, but that wasn't any big deal. Here is my modified below:

{composition-setup}

{report-block:style=disc|firstResult=1}
{content-reporter:type=page|space=@self|label=+book}
 {text-sort:content:title|mode=natural|order=ascending}
{content-reporter}

{report-header}
{deck:id=Shelves}
{report-header}

{repeat-filter:content:title > first 1 > upper case case}
{report-body:injected=true}
{card:title=%content:title > first 1 > upper case%}
{report-body}

{report-body}
h5. _{report-info:content:title|link=true}_  {report-info:data:BookSubTitle} {report-info:data:Read|render=wiki}
-- *by {report-info:data:Author}*
_Abstract:_ {report-info:content:excerpt}
{report-body}

{repeat-filter:content:title > first 1 > upper case case}
{report-body}
{card}
{report-body}

{report-footer}
{deck}
{report-footer}

{report-empty}_There are no books available._{report-empty}

{report-block}

The result of the report-block is the same thing as I had without the header and footer, or any filters, except it now has a box around it. Like it's wanting to create cards but it doesn't. Or something like that.

Thanks for your help.

I'm not sure if it is list data.  Maybe if i describe the situation a little better you can tell.

The Hierarchy:
>Space

>> 4 Children off the Home (2 of which will be referred to as Missions and Instruments)

>>> Unlimited Children to be added to these subgroups as any Confluence user sees fit (2 of which will be referred to as Mission 1 and Instrument 1 which are children of Missions and Instruments respectively)

 The Goal:

Since the individual children in the Missions subgroup are intended to be an overview of all aspects of a mission, information on the Instruments children associated is also desired.  What we desire to display on the Mission 1 page is a table of information that is created in Instrument 1 when Instrument 1 is created.

 The Challenge:

This would be a simple matter if Instrument 1 already existed and we could "hard code" a name into a local-reporter|text-filter|report-table combo, but there are 3 problems with this.

1) We don't want the casual confluence user to have to go into the 'Edit Layout' mode and change the local-reporter|text-filter|report-table code themselves,

2) If Instrument 1 doesn't exist yet in the first place and will be added later, there is nothing yet there to report on, and

3) Since we don't want to grab every single data table from every single Instruments child, and since we need to write this reporter generically in a template that varies the filter to only search for Instruments children that contain a string of characters associated with the specific Missions child (e.g. Mission 1 only wanting to report info on Instrument 1 and not a supposed Instrument X, but then another supposed Mission X is created using the same template as Mission 1 but will only report info from Instruments it is associated with, like Instrument X)

This would suggest that in our template we need a filter that has a variable as its regular expression, one that pulls the title of Mission 1 (or Mission X as the case may be) and filters through Instruments children looking for instances of this title that the user will be prompted to fill in when creating an Instruments child (i.e. if Instrument 1 is interested in Mission 1, then Mission 1's title will be provided somewhere in Instrument 1's table to be reported).

I've had difficulty with this because if you try a text-filter with include={report-info:content:title} it simply displays the code rather than grabbing Mission 1's title and using it as the filter parameter.

One last piece of info, the table in Instrument 1 is generated via an editable table code and is subsequently filled upon generation of the Instruments child.

Sorry for the long-winded and probably painfully non-technical reply, just wanted to make sure my intent was portrayed and I'm working on a limited comp sci vocab here .