{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":165413896,"defaultBranch":"master","name":"arches-docs","ownerLogin":"OpenTechStrategies","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2019-01-12T17:10:14.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/1455458?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1713509609.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"eced4fbfca7453c0ec751486f90737e2f21be8e2","ref":"refs/heads/typo-fixes","pushedAt":"2024-04-19T06:53:29.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Fix a few typos","shortMessageHtmlLink":"Fix a few typos"}},{"before":"245f9d378412b080ae57d4032e61773f9186e381","after":"90185d1c9507de11356ff29125d98464347d8a94","ref":"refs/heads/master","pushedAt":"2024-04-19T06:41:58.000Z","pushType":"push","commitsCount":172,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Merge pull request #408 from archesproject/jtw/remove-this\n\nRemove advice to use `this` in vue templates","shortMessageHtmlLink":"Merge pull request <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"2241037495\" data-permission-text=\"Title is private\" data-url=\"https://github.com/archesproject/arches-docs/issues/408\" data-hovercard-type=\"pull_request\" data-hovercard-url=\"/archesproject/arches-docs/pull/408/hovercard\" href=\"https://github.com/archesproject/arches-docs/pull/408\">archesproject#408</a> from archesproject/jtw/remove-this"}},{"before":null,"after":"42e4ff00ab993d1620ece426cee75ac05609f924","ref":"refs/heads/master_document_id_naming_conventions","pushedAt":"2023-05-23T21:43:27.724Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Add new section: Naming Conventions\n\nRight now, this new section just holds one subsection, documenting one\nconvention: \"``id`` vs ``_id``: ID as Primary Key vs Foreign Key\" (as\ndiscussed in PR #345).  There are probably other naming conventions in\nthe Arches code, though, and now at least there's a place to document\nthem when we think of them (although it remains to be seen whether\n\"Data Model\" is the right place for all this -- perhaps the entire\n\"Naming Conventions\" section will need to be moved eventually).","shortMessageHtmlLink":"Add new section: Naming Conventions"}},{"before":"2102cca10848125aa8a8dc2c21fe69c18f96324f","after":"5e86f898dac701b9e38dae330755257d8230c02f","ref":"refs/heads/nodegroupid-to-nodegroup_id","pushedAt":"2023-05-23T19:43:37.803Z","pushType":"push","commitsCount":1,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Revert some doc changes from commit 2102cca10848\n\nAs per @mradamcox's and @ekansa's review in PR #345, the changes to\nthe workflow documentation in commit 2102cca10848 were incorrect; this\nreverts those changes.  The fixes to the import/export section still\nlook right, however -- I checked them over again in light of the\nreview -- so this commit leaves them in place.","shortMessageHtmlLink":"Revert some doc changes from commit <a class=\"commit-link\" data-hovercard-type=\"commit\" data-hovercard-url=\"https://github.com/OpenTechStrategies/arches-docs/commit/2102cca10848125aa8a8dc2c21fe69c18f96324f/hovercard\" href=\"https://github.com/OpenTechStrategies/arches-docs/commit/2102cca10848125aa8a8dc2c21fe69c18f96324f\"><tt>2102cca</tt></a>"}},{"before":"4f8a538e672d0b2e7434419be27002e5e4835e81","after":"2102cca10848125aa8a8dc2c21fe69c18f96324f","ref":"refs/heads/nodegroupid-to-nodegroup_id","pushedAt":"2023-05-19T01:49:39.806Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Say \"nodegroup_id\" instead of \"nodegroupid\"\n\nThis edits various places in the documentation where (I believe) we\nshould recommend \"nodegroup_id\" instead of \"nodegroupid\" in JSON.\nWhen our team did a batch import of images guided by the documentation\npublished at https://arches.readthedocs.io/en/7.3/import-export, the\nexisting instructions to use \"nodegroupid\" in JSON didn't work; when\nwe switched our JSON to use \"nodegroup_id\", it worked.\n\nStill, I'm not 100% sure this change is correct and would definitely\nlike some review.  Once that review is done, if the change looks\ncorrect then I'll just amend this commit message before we merge.\n\nHere are some more details:\n\nIn the Arches source code tree, both \"nodegroupid\" and \"nodegroup_id\"\neach appear plenty of times, though the latter more often:\n\n  - \"nodegroupid\"  in arches source:  1011 occurrences (21%)\n  - \"nodegroup_id\" in arches source:  3798 occurrences (79%)\n\nMeanwhile, in the Arches documentation, both terms also appear --\nthough, curiously, in exactly reversed proportion!\n\n  - \"nodegroupid\"  in arches docs:      44 occurrences (79%)\n  - \"nodegroup_id\" in arches docs:      12 occurrences (21%)\n\nAs far as I can tell, what's going on is that within the database\nitself (e.g., in tables like 'cards', 'nodes', 'edit_log', 'tiles',\nand 'nodegroup') the column name is always \"nodegroupid\".  However, in\nplaces where nodegroup IDs are to be accepted or expressed from/to\ntextual sources (e.g., in JSON input or output), then \"nodegroup_id\"\nis generally used and, somewhere along the way, gets converted over.\n\n(But again, I'm not 100% sure that this pattern is real.  It's just an\neducated guess, and I'd appreciate more knowledgeable heads evaluating\nthese statements.)\n\nSo for example, 'arches/db/dml/db_data.sql' in the arches source code:\n\n  INSERT INTO functions(functionid, modulename, classname,\n                        functiontype, name, description,\n                        defaultconfig, component)\n      VALUES ('60000000-0000-0000-0000-000000000001',\n              'primary_descriptors.py',\n              'PrimaryDescriptorsFunction',\n              'primarydescriptors',\n              'Define Resource Descriptors',\n              'Configure the name, description, and map popup of a resource',\n              '{\"module\": \"arches.app.functions.primary_descriptors\",\n                \"class_name\":\"PrimaryDescriptorsFunction\",\n                \"descriptor_types\":\n                 {\"name\": {\"nodegroup_id\": \"\", \"string_template\": \"\"},\n                \"description\": {\"nodegroup_id\": \"\", \"string_template\":\"\"},\n                \"map_popup\": {\"nodegroup_id\": \"\", \"string_template\":\"\"}} }',\n              'views/components/functions/primary-descriptors');\n\n(Line breaks added to fit commit message width constraints.)\n\nBesides that conversion-from-textual-source pattern, \"nodegroup_id\" is\nalso sometimes used in the Arches source code for variable names;\ne.g., search for it in 'tests/utils/label_based_graph_test'.\n\nBut even then, there are still some things that puzzle me, given the\nabove broad patterns (which, again, are highly tentative and I'm not\nsure I've correctly deduced them).  For example, there's this line in\n'arches/management/commands/load_jsonld.py':\n\n  \"nodegroupid\": tile.nodegroup_id,\n\nThere's similar stuff in 'arches/app/media/js/viewmodels/tile.js',\n'arches/management/commands/etl_template.py', and\n'tests/importer/jsonld_import_tests.py', and other files.\n\nAnyway, in this documentation change, I've left \"nodegroupid\"\nuntouched in these files...\n\n  - docs/images/datamodel-arches-4.4.1-032119.svg\n  - docs/images/datamodel-full-4.4.1-032119.svg\n  - docs/examples/arches/node.py\n  - docs/examples/arches/editlog.py\n  - docs/examples/arches/cardmodel.py\n  - docs/examples/arches/tilemodel.py\n  - docs/examples/arches/nodegroup.py\n  - docs/examples/arches/nodegroup.py\n\n...because in those contexts it appears to be correct.","shortMessageHtmlLink":"Say \"nodegroup_id\" instead of \"nodegroupid\""}},{"before":"172898459634f0d2f0f9fbbd776729c7cda3e26b","after":"4f8a538e672d0b2e7434419be27002e5e4835e81","ref":"refs/heads/nodegroupid-to-nodegroup_id","pushedAt":"2023-05-18T23:36:49.513Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Say \"nodegroup_id\" instead of \"nodegroupid\"\n\nThis edits various places in the documentation where (I believe) we\nshould recommend \"nodegroup_id\" instead of \"nodegroupid\" in JSON.\nWhen our team did a batch import of images guided by the documentation\npublished at https://arches.readthedocs.io/en/7.3/import-export, the\nexisting instructions to use \"nodegroupid\" in JSON didn't work; when\nwe switched our JSON to use \"nodegroup_id\", it worked.\n\nStill, I'm not 100% sure this change is correct and would definitely\nlike some review.  Once that review is done, if the change looks\ncorrect then I'll just amend this commit message before we merge.\n\nHere are some more details:\n\nIn the Arches source code tree, both \"nodegroupid\" and \"nodegroup_id\"\neach appear plenty of times, though the latter more often:\n\n  - \"nodegroupid\"  in arches source:  1011 occurrences (21%)\n  - \"nodegroup_id\" in arches source:  3798 occurrences (79%)\n\nMeanwhile, in the Arches documentation, both terms also appear --\nthough, curiously, in exactly reversed proportion!\n\n  - \"nodegroupid\"  in arches docs:      44 occurrences (79%)\n  - \"nodegroup_id\" in arches docs:      12 occurrences (21%)\n\nAs far as I can tell, what's going on is that within the database\nitself (e.g., in tables like 'cards', 'nodes', 'edit_log', 'tiles',\nand 'nodegroup') the column name is always \"nodegroupid\".  However, in\nplaces where nodegroup IDs are to be accepted or expressed from/to\ntextual sources (e.g., in JSON input or output), then \"nodegroup_id\"\nis generally used and, somewhere along the way, gets converted over.\n\n(But again, I'm not 100% sure that this pattern is real.  It's just an\neducated guess, and I'd appreciate more knowledgeable heads evaluating\nthese statements.)\n\nSo for example, 'arches/db/dml/db_data.sql' in the arches source code:\n\n  INSERT INTO functions(functionid, modulename, classname,\n                        functiontype, name, description,\n                        defaultconfig, component)\n      VALUES ('60000000-0000-0000-0000-000000000001',\n              'primary_descriptors.py',\n              'PrimaryDescriptorsFunction',\n              'primarydescriptors',\n              'Define Resource Descriptors',\n              'Configure the name, description, and map popup of a resource',\n              '{\"module\": \"arches.app.functions.primary_descriptors\",\n                \"class_name\":\"PrimaryDescriptorsFunction\",\n                \"descriptor_types\":\n                 {\"name\": {\"nodegroup_id\": \"\", \"string_template\": \"\"},\n                \"description\": {\"nodegroup_id\": \"\", \"string_template\":\"\"},\n                \"map_popup\": {\"nodegroup_id\": \"\", \"string_template\":\"\"}} }',\n              'views/components/functions/primary-descriptors');\n\n(Line breaks added fit commit message width constraints.)\n\nBesides that conversion-from-textual-source pattern, \"nodegroup_id\" is\nalso sometimes used in the Arches source code for variable names;\ne.g., search for it in 'tests/utils/label_based_graph_test'.\n\nBut even then, there are still some things that puzzle me, given the\nabove broad patterns (which, again, are highly tentative and I'm not\nsure I've correctly deduced them).  For example, there's this line in\n'arches/management/commands/load_jsonld.py':\n\n  \"nodegroupid\": tile.nodegroup_id,\n\nThere's similar stuff in 'arches/app/media/js/viewmodels/tile.js',\n'arches/management/commands/etl_template.py', and\n'tests/importer/jsonld_import_tests.py', and other files.\n\nAnyway, in this documentation change, I've left \"nodegroupid\"\nuntouched in these files...\n\n  - docs/images/datamodel-arches-4.4.1-032119.svg\n  - docs/images/datamodel-full-4.4.1-032119.svg\n  - docs/examples/arches/node.py\n  - docs/examples/arches/editlog.py\n  - docs/examples/arches/cardmodel.py\n  - docs/examples/arches/tilemodel.py\n  - docs/examples/arches/nodegroup.py\n  - docs/examples/arches/nodegroup.py\n\n...because in those contexts it appears to be correct.","shortMessageHtmlLink":"Say \"nodegroup_id\" instead of \"nodegroupid\""}},{"before":null,"after":"172898459634f0d2f0f9fbbd776729c7cda3e26b","ref":"refs/heads/nodegroupid-to-nodegroup_id","pushedAt":"2023-05-18T20:31:01.998Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Say \"nodegroup_id\" instead of \"nodegroupid\"\n\nThis edits various places in the documentation where (I believe) we\nshould recommend \"nodegroup_id\" instead of \"nodegroupid\" in JSON.\nWhen our team did a batch import of images guided by the documentation\npublished at https://arches.readthedocs.io/en/7.3/import-export, the\nexisting instructions to use \"nodegroupid\" in JSON didn't work; when\nwe switched our JSON to use \"nodegroup_id\", it worked.\n\nStill, I'm not 100% sure this change is correct and would definitely\nlike some review.  Once that review is done, if the change looks\ncorrect then I'll just amend this commit message before we merge.\n\nHere are some more details:\n\nIn the Arches source code tree, both \"nodegroupid\" and \"nodegroup_id\"\neach appear plenty of times, though the latter more often:\n\n  - \"nodegroupid\"  in arches source:  1011 occurrences (21%)\n  - \"nodegroup_id\" in arches source:  3798 occurrences (79%)\n\nMeanwhile, in the Arches documentation, both terms also appear --\nthough, curiously, in exactly reversed proportion!\n\n  - \"nodegroupid\"  in arches docs:      44 occurrences (79%)\n  - \"nodegroup_id\" in arches docs:      12 occurrences (21%)\n\nAs far as I can tell, what's going on is that within the database\nitself (e.g., in tables like 'cards', 'nodes', 'edit_log', 'tiles',\nand 'nodegroup') the column name is always \"nodegroupid\".  However, in\nplaces where nodegroup IDs are to be accepted or expressed from/to\ntextual sources (e.g., in JSON input or output), then \"nodegroup_id\"\nis generally used and, somewhere along the way, gets converted over.\n\n(But again, I'm not 100% sure that this pattern is real.  It's just an\neducated guess, and I'd appreciate more knowledgeable heads evaluating\nthese statements.)\n\nSo for example, 'arches/db/dml/db_data.sql' in the arches source code:\n\n  INSERT INTO functions(functionid, modulename, classname,\n                        functiontype, name, description,\n                        defaultconfig, component)\n      VALUES ('60000000-0000-0000-0000-000000000001',\n              'primary_descriptors.py',\n              'PrimaryDescriptorsFunction',\n              'primarydescriptors',\n              'Define Resource Descriptors',\n              'Configure the name, description, and map popup of a resource',\n              '{\"module\": \"arches.app.functions.primary_descriptors\",\n                \"class_name\":\"PrimaryDescriptorsFunction\",\n                \"descriptor_types\":\n                 {\"name\": {\"nodegroup_id\": \"\", \"string_template\": \"\"},\n                \"description\": {\"nodegroup_id\": \"\", \"string_template\":\"\"},\n                \"map_popup\": {\"nodegroup_id\": \"\", \"string_template\":\"\"}} }',\n              'views/components/functions/primary-descriptors');\n\n(Line breaks added fit commit message width constraints.)\n\nBesides that conversion-from-textual-source pattern, \"nodegroup_id\" is\nalso sometimes used in the Arches source code for variable names;\ne.g., search for it in 'tests/utils/label_based_graph_test'.\n\nBut even then, there are still some things that puzzle me, given the\nabove broad patterns (which, again, are highly tentative and I'm not\nsure I've correctly deduced them).  For example, there's this line in\n'arches/management/commands/load_jsonld.py':\n\n  \"nodegroupid\": tile.nodegroup_id,\n\nThere's similar stuff in 'arches/app/media/js/viewmodels/tile.js',\n'arches/management/commands/etl_template.py', and\n'tests/importer/jsonld_import_tests.py', and other files.\n\nAnyway, in this documentation change, I've left \"nodegroupid\"\nuntouched in these files...\n\n  - docs/images/datamodel-arches-4.4.1-032119.svg\n  - docs/images/datamodel-full-4.4.1-032119.svg\n  - docs/examples/arches/node.py\n  - docs/examples/arches/editlog.py\n  - docs/examples/arches/cardmodel.py\n  - docs/examples/arches/tilemodel.py\n  - docs/examples/arches/nodegroup.py\n  - docs/examples/arches/nodegroup.py\n\n...because in those contexts it appears to be correct.","shortMessageHtmlLink":"Say \"nodegroup_id\" instead of \"nodegroupid\""}},{"before":"44a51eb0a0bf92e872d3197d0299ba1a225e84f5","after":"245f9d378412b080ae57d4032e61773f9186e381","ref":"refs/heads/master","pushedAt":"2023-05-18T19:45:28.788Z","pushType":"push","commitsCount":260,"pusher":{"login":"kfogel","name":"Karl Fogel","path":"/kfogel","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/401111?s=80&v=4"},"commit":{"message":"Added note about Nginx client_max_body_size","shortMessageHtmlLink":"Added note about Nginx client_max_body_size"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wNC0xOVQwNjo1MzoyOS4wMDAwMDBazwAAAAQ03Nta","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wNS0xOFQxOTo0NToyOC43ODgwMTdazwAAAAMvraRU"}},"title":"Activity · OpenTechStrategies/arches-docs"}