uniform_resource_file (view) Content
| 01JFW585KSEVK6AD03R42XNCF5 | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/cgm_tracing.csv | 158475577 |
| 01JFW585VNJCC92NVA2PZ570JB | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/lab.csv | 56 |
| 01JFW585VNG95ZWYDFQRW7MYMZ | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/institution.csv | 171 |
| 01JFW585VNY4VRRBXXGSAJA3D6 | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/cgm_file_metadata.csv | 11332 |
| 01JFW585VNE3KNBNXAPPWM40GF | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/investigator.csv | 1587 |
| 01JFW585VNM61QVFZ0E4R94C2B | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/study.csv | 865 |
| 01JFW585VNZE1PBKSJS79RPT4J | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/site.csv | 46 |
| 01JFW585VNKPQ8JX1GA9VS4BRG | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/publication.csv | 233 |
| 01JFW585VNPX23GGC1X6YCJWJ9 | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/author.csv | 280 |
| 01JFW585VPX3JNPQCJ5Q9GHVZM | csv | /app/www.surveilr.com/lib/pattern/research-study-explorer/dclp1 | dclp1/participant.csv | 14081 |
Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.
Error in query number 6:
Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:
SELECT 'text' AS component,
(SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
⬆️
'(Page ' || $current_page || ' of ' || $total_pages || ') ' ||
Backtrace
sql parser error: Expected: END, found: ' ||
' at Line: 42, Column: 149"console/content/view/uniform_resource_file.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.