1 Topic by Ambulare

  • Ambulare
  • Member
  • Offline
  • Registered: 24-03-2014
  • Posts: 32

Topic: A couple more indicia questions

Hi all,

Thanks for you help so far in setting up a new site, but I've got a couple more questions...

After your previous advice, I'm now upgraded to Drupal 7 with the latest versions of the Indicia Forms modules, rather than using Instant Indicia. However, I'm still rather inexperienced with both Indicia and Drupal!

1. I'd like to give logged in users a "My Records" page that shows them the sightings they've entered along with any images uploaded to each sighting. The reports I've found so far seem to have predefined fields that don't necessarily match the information I've asked users to enter and don't come with sighting images (e.g. I don't need "Zero Abundance" or "Common" but it would be nice to add some of the custom fields from my survey instead). Is there a suitable dynamic report that would fulfil my requirements?

2. If/when I move this project from the test warehouse to the live warehouse, will I be able to set up validation so that my colleagues be able to validate the records through iRecord, sparing the need for a custom validation process in my site? I read the website agreements page in the documentation, (http://indicia-docs.readthedocs.org/en/ … ments.html) but I'm not clear whether this would provide my data to *all* iRecord users to validate, which seems a little too broad an audience for specialised data.

Thanks again,

Steve

2 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: A couple more indicia questions

Hi Steve
For question 1, would the iRecord style My Records suit your purpose? If so, then you need to create a Dynamic Report Explorer page, and specify the following under User Interface > Form configuration:

[standard_params]
@allowSave=true
@linkToMapDiv=map
@taxon_list_id=15
@filter-my_records=1
@indexedLocationTypeIds=[15,1370]
@otherLocationTypeIds=[2412,2188]
[map]
@dataSource=library/occurrences/filterable_explore_list_mapping
@dataSourceLoRes=library/occurrences/filterable_explore_list_mapping_lores
=Records=
[report_grid]
@dataSource=library/occurrences/filterable_explore_list
@rowId=occurrence_id
@downloadLink=true
=Species=
[report_grid]
@id=species
@dataSource=library/taxa/filterable_explore_list
@downloadLink=true
@rowId=taxon_meaning_id
@linkFilterToMap=false
=Taxon groups=
[report_grid]
@id=taxon_groups
@dataSource=library/taxon_groups/filterable_explore_list
@downloadLink=true
@rowId=taxon_group_id
@linkFilterToMap=false
=Families=
<p>This report shows a breakdown of the species and record counts by taxonomic family.</p>
[report_grid]
@id=families
@dataSource=library/taxa/filterable_explore_list_taxonomy_breakdown
@downloadLink=true
@linkFilterToMap=false
=Photos=
[report_grid]
@id=photos
@dataSource=library/occurrence_images/filterable_explore_list
@rowId=occurrence_id
@includeAllColumns=false
@headers=false
@galleryColCount=4
@itemsPerPage=16

Under the report settings, preset parameters specify the following:

smpattrs=
occattrs=
default_input_form=enter-record-list
my_records=1

You'll of course need to tweak map and other settings to your liking but hopefully that will get you started.

If you need to remove a column from the first records grid for example, then under Report Settings > Columns Configuration List, click Add Columns List to Column Configuration List (this adds a container for a list of column definitions that will control behaviour of the first grid on the page). Now, add columns to this list and for each, add the fieldname property and set it to the fieldname output by the report, and add the visible checkbox property and leave it unchecked.

If you want to add your own custom attribute columns to the report, then specify the attribute IDs under the smpattrs and occattrs as a comma separated list, in the preset parameters setting as described above.

2. When you expose your records to verification in iRecord, they will only appear on the verification screens which only verifiers can see, not all users. Each verifier has a taxonomic and geographic filter as appropriate, so they will only see the records which suit their expertise.

Best wishes
John

John van Breda
Biodiverse IT

johnvanbreda's Website