Subversion Repositories oidplus

Rev

Rev 1143 | Rev 1149 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 1143 Rev 1148
Line 5... Line 5...
5
- Nullable params passed to non-nullable methods => find using PHPStan level 7
5
- Nullable params passed to non-nullable methods => find using PHPStan level 7
6
 
6
 
7
April 2023 planned:
7
April 2023 planned:
8
- Don't send information object OIDs to oid-info.com anymore
8
- Don't send information object OIDs to oid-info.com anymore
9
- https://github.com/danielmarschall/oidplus/issues/5 => "Offline mode" (do not contact internet, e.g. gs1-barcodes, polyfill, oidinfo, ...)
9
- https://github.com/danielmarschall/oidplus/issues/5 => "Offline mode" (do not contact internet, e.g. gs1-barcodes, polyfill, oidinfo, ...)
-
 
10
	make function url_post_contents() which abstracts cURL
10
 
11
 
11
Admin Auth:
12
Admin Auth:
12
- implement argon2 as alternative to bcrypt?
13
- implement argon2 as alternative to bcrypt?
13
- idea: could RA-auth-plugins also be used to create the admin-hash? problem: setup/ generates hash with javascript, not via PHP!!!
14
- idea: could RA-auth-plugins also be used to create the admin-hash? problem: setup/ generates hash with javascript, not via PHP!!!
14
- BCrypt
15
- BCrypt
Line 176... Line 177...
176
- freeoid: hide asn.1 and iri columns, because the RA is not allocating these identifiers?
177
- freeoid: hide asn.1 and iri columns, because the RA is not allocating these identifiers?
177
- .... maybe we should have a list of OIDs where the OID does not allocate ASN.1/IRI identifiers... then we can also make use of the OID-WHOIS attributes
178
- .... maybe we should have a list of OIDs where the OID does not allocate ASN.1/IRI identifiers... then we can also make use of the OID-WHOIS attributes
178
- Privacy flag of RAs: Should there be more privacy levels, e.g. that you don't show your personal name etc.?
179
- Privacy flag of RAs: Should there be more privacy levels, e.g. that you don't show your personal name etc.?
179
- You should be able to change the "created" date for an object! Or maybe hide it completely if you don't know the original creation date?
180
- You should be able to change the "created" date for an object! Or maybe hide it completely if you don't know the original creation date?
180
- In the CRUD table, you should be able to see the name of the OID? But on the other hand, the title is not in the control of the Superior RA, and the CRUD table is actually the allocation table of the Superior RA.
181
- In the CRUD table, you should be able to see the name of the OID? But on the other hand, the title is not in the control of the Superior RA, and the CRUD table is actually the allocation table of the Superior RA.
181
- natOrder() does only work for OID namespace!!! other sort mechanisms are necessary for other object types
-
 
182
- jstree select: automatically scroll down
182
- jstree select: automatically scroll down
183
- jstree: right click "open in new tab" is not possible
183
- jstree: right click "open in new tab" is not possible
184
- things like RA: show more things, address, email etc.
184
- things like RA: show more things, address, email etc.
185
- note that we (and the Internet Draft) talk about Objects, but actually OIDs only reference objects, but they are not the objects
185
- note that we (and the Internet Draft) talk about Objects, but actually OIDs only reference objects, but they are not the objects
186
- Multilang
186
- Multilang
Line 201... Line 201...
201
	The GIT version might be behind the master SVN repository
201
	The GIT version might be behind the master SVN repository
202
	So if you do "git pull", the update/index.php page might still show that an update is available!
202
	So if you do "git pull", the update/index.php page might still show that an update is available!
203
- add some kind of loading cricle animation or a progress bar during the update
203
- add some kind of loading cricle animation or a progress bar during the update
204
 
204
 
205
DATABASE
205
DATABASE
206
- SQLite3: Implement Natural OID sorting (natSort)
-
 
207
- make usage of Foreign Keys
206
- make usage of Foreign Keys
208
	PROBLEM: we need foreign keys with no check, because
207
	PROBLEM: we need foreign keys with no check, because
209
	a) we want to keep log entries even if an object/user is deleted
208
	a) we want to keep log entries even if an object/user is deleted
210
	b) log_user.username can also be 'admin' (and therefore not be a foreign key to table 'ra')
209
	b) log_user.username can also be 'admin' (and therefore not be a foreign key to table 'ra')
211
	c) not every object should have a registered RA. There should be "unknown" RAs where only the email address is known
210
	c) not every object should have a registered RA. There should be "unknown" RAs where only the email address is known